GNU bug report logs - #7969
Lisp nesting exceeds `max-lisp-eval-depth' in ibuffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7969 in the body.
You can then email your comments to 7969 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: mxemacs <at> Safe-mail.net
To: bug-gnu-emacs <at> gnu.org
Subject: Lisp nesting exceeds `max-lisp-eval-depth' in ibuffer
Date: Wed, 2 Feb 2011 14:00:52 -0500

[Message part 1 (text/plain, inline)]

emacs' ibuffer mode crashes on my machine (Win32, GNU Emacs 24.0.50.1 (i386-mingw-nt6.1.7600) of 2011-01-31 on 3249CTO) when used with complex saved filters. I attached a minimal sample that reproduces the error on a vanilla emacs installation (--no-init-file, built from http://alpha.gnu.org/gnu/emacs/windows/)

[ibt.el (text/x-emacs-lisp, attachment)]

Message #8 received at 7969 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: mxemacs <at> Safe-mail.net
Cc: 7969 <at> debbugs.gnu.org
Subject: Re: bug#7969: Lisp nesting exceeds `max-lisp-eval-depth' in ibuffer
Date: Wed, 02 Feb 2011 18:53:01 -0500

mxemacs <at> Safe-mail.net wrote:

> emacs' ibuffer mode crashes on my machine (Win32, GNU Emacs 24.0.50.1
> (i386-mingw-nt6.1.7600) of 2011-01-31 on 3249CTO) when used with
> complex saved filters. I attached a minimal sample that reproduces the
> error on a vanilla emacs installation (--no-init-file, built from
> http://alpha.gnu.org/gnu/emacs/windows/)

I've never used this feature, but perhaps there is a typo in your
configuration (extra set of parens in group "5")?
Using the following diff, the problem goes away:


*** ibt.el.BAK	2011-02-02 15:50:30.000000000 -0800
--- ibt.el	2011-02-02 15:50:36.000000000 -0800
***************
*** 10,18 ****
  		  (mode . eshell-mode)))
  	 ("4" (or (name . "^\\*scratch\\*$")
  		  (name . "^\\*Messages\\*$")))
! 	 ("5" ((or (name . "^\\*gnus trace\\*$")
  		   (name . "^\\*imap log\\*$")
! 		   (name . "^\\.newsrc-dribble$")))))))
  (get-buffer-create ".newsrc-dribble")
  (get-buffer-create "*Compile-Log*")
  (get-buffer-create "*Completions*")
--- 10,18 ----
  		  (mode . eshell-mode)))
  	 ("4" (or (name . "^\\*scratch\\*$")
  		  (name . "^\\*Messages\\*$")))
! 	 ("5" (or (name . "^\\*gnus trace\\*$")
  		   (name . "^\\*imap log\\*$")
! 		   (name . "^\\.newsrc-dribble$"))))))
  (get-buffer-create ".newsrc-dribble")
  (get-buffer-create "*Compile-Log*")
  (get-buffer-create "*Completions*")

Message #11 received at 7969 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 7969 <at> debbugs.gnu.org, mxemacs <at> Safe-mail.net
Subject: Re: bug#7969: Lisp nesting exceeds `max-lisp-eval-depth' in ibuffer
Date: Wed, 02 Feb 2011 21:12:23 -0500

>> emacs' ibuffer mode crashes on my machine (Win32, GNU Emacs 24.0.50.1
>> (i386-mingw-nt6.1.7600) of 2011-01-31 on 3249CTO) when used with
>> complex saved filters. I attached a minimal sample that reproduces the
>> error on a vanilla emacs installation (--no-init-file, built from
>> http://alpha.gnu.org/gnu/emacs/windows/)

> I've never used this feature, but perhaps there is a typo in your
> configuration (extra set of parens in group "5")?
> Using the following diff, the problem goes away:

Indeed, that looks like a likely trigger, but it's still a bug for
ibuffer to inf-loop when faced with such data.  Can you investigate to
try and avoid the inf-loop?


        Stefan

Message #16 received at 7969-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 7969-done <at> debbugs.gnu.org
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#7969: Lisp nesting exceeds `max-lisp-eval-depth' in ibuffer
Date: Thu, 03 Feb 2011 02:03:08 -0500

Version: 23.3

Stefan Monnier wrote:

> Indeed, that looks like a likely trigger, but it's still a bug for
> ibuffer to inf-loop when faced with such data.  Can you investigate to
> try and avoid the inf-loop?

Fixed.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.