From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: 23.0.60; vc inflooping Date: Sun, 04 May 2008 19:55:47 -0400 Message-ID: <877ie9lj3w.fsf@maru.md5i.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1209945385 5322 80.91.229.12 (4 May 2008 23:56:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 May 2008 23:56:25 +0000 (UTC) To: emacs-pretest-bug@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 05 01:57:02 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jso4i-0004ui-JE for ged-emacs-devel@m.gmane.org; Mon, 05 May 2008 01:57:00 +0200 Original-Received: from localhost ([127.0.0.1]:50329 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jso41-00031S-2x for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 19:56:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jso3w-0002xh-0J for emacs-devel@gnu.org; Sun, 04 May 2008 19:56:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jso3r-0002qh-PO for emacs-devel@gnu.org; Sun, 04 May 2008 19:56:11 -0400 Original-Received: from [199.232.76.173] (port=45372 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jso3r-0002qQ-2m for emacs-devel@gnu.org; Sun, 04 May 2008 19:56:07 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jso3q-00044D-Qz for emacs-devel@gnu.org; Sun, 04 May 2008 19:56:06 -0400 Original-Received: from mx10.gnu.org ([199.232.76.166]:39995) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1Jso3L-0000Tc-NR for emacs-pretest-bug@gnu.org; Sun, 04 May 2008 19:55:35 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Jso3m-00043a-W9 for emacs-pretest-bug@gnu.org; Sun, 04 May 2008 19:56:06 -0400 Original-Received: from md5i.com ([66.207.132.105] helo=maru.md5i.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jso3m-000411-8t for emacs-pretest-bug@gnu.org; Sun, 04 May 2008 19:56:02 -0400 Original-Received: from md5i by maru.md5i.com with local (Exim 4.69) (envelope-from ) id 1Jso3Y-0001Dg-3o for emacs-pretest-bug@gnu.org; Sun, 04 May 2008 19:55:48 -0400 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96466 gmane.emacs.pretest.bugs:22201 Archived-At: Please describe exactly what actions triggered the bug and the precise symptoms of the bug: emacs -Q C-x C-f /tmp/foo RET This is a test file C-x C-s C-x v i yes RET C-x v v Symptoms: find-auto-coding: Variable binding depth exceeds max-specpdl-size max-specpdl-size is a variable defined in `C source code'. Its value is 1040 M-: (setq max-specpdl-size 2000) C-x v v [in buffer foo] Same error M-: (setq max-specpdl-size 10000) C-x v v [in buffer foo] find-auto-coding: Lisp nesting exceeds `max-lisp-eval-depth' max-lisp-eval-depth is a variable defined in `C source code'. Its value is 400 M-: (setq max-lisp-eval-depth 10000) Emacs takes a long, long time. C-g M-x toggle-debug-on-quit C-x v v [wait a couple seconds] C-g Bottom of *Bactrace* buffer: vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) apply(vc-rcs-checkout-model ("/tmp/foo")) vc-call-backend(RCS checkout-model ("/tmp/foo")) vc-checkout-model(RCS ("/tmp/foo")) vc-next-action(nil) call-interactively(vc-next-action nil nil) So, there's an infloop happening. In GNU Emacs 23.0.60.6 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-04 on maru Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--without-toolkit-scroll-bars' '--with-dbus' '--enable-font-backend'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.utf8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Emacs-Lisp Minor modes in effect: display-time-mode: t shell-dirtrack-mode: t senator-minor-mode: t semantic-idle-summary-mode: t semantic-idle-scheduler-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t Recent input: C-p C-p C-p C-p C-p > C-p C-p C-p C-p C-p C-p C-f C-f M-x d e b u g - o n q M-x C-g C-g C-x C-g q M-x t o g g l e - d e q C-x v v d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c c c c d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c c c c d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c d d d d d d d d d d d d d d d d d d q M-x C-g C-g M-x r e p o r t - e m Recent messages: Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Back to top level. Don't touch it! It's the History Eraser Button, you fool! [2 times] -- Michael Welsh Duggan (md5i@cs.cmu.edu)