GNU bug report logs - #31286
26.1; edebug prevents closing

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 31286 in the body.
You can then email your comments to 31286 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: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.1; edebug prevents closing
Date: Fri, 27 Apr 2018 10:24:57 +0200

Hi, this is a very old issue, don't see it at https://debbugs.gnu.org/:

when closing a file where a function was instrumented running edebug, 
Emacs refuses to get shut down afterwards. After answering the common 
closing questionaire, a buffer appears again and again showing

Debugger entered: nil
  edebug--display-1(nil 0 before)
  edebug--display(nil 0 before)
  edebug-debugger(0 before nil)
  edebug-before(0)
  ...

and thats it.

In GNU Emacs 26.1 (build 1, i686-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2018-04-10

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 31286 <at> debbugs.gnu.org
Subject: Re: bug#31286: 26.1; edebug prevents closing
Date: Fri, 27 Apr 2018 11:46:22 +0300

> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
> Date: Fri, 27 Apr 2018 10:24:57 +0200
> 
> Hi, this is a very old issue, don't see it at https://debbugs.gnu.org/:
> 
> when closing a file where a function was instrumented running edebug, 
> Emacs refuses to get shut down afterwards. After answering the common 
> closing questionaire, a buffer appears again and again showing
> 
> Debugger entered: nil
>    edebug--display-1(nil 0 before)
>    edebug--display(nil 0 before)
>    edebug-debugger(0 before nil)
>    edebug-before(0)
>    ...
> 
> and thats it.

I can reproduce this only partially.  After killing the buffer that
visits the file whose function was instrumented using edebug-defun, I
indeed see an error and a backtrace when I invoke a command which
calls that function.  But I have no problem shutting down Emacs,
either before or after the backtrace pops up.

So I'm guessing some other customization of yours is involved; please
try in "emacs -Q" to see if your observations are different from mine.

If you can reproduce this starting with "emacs -Q", please show a
recipe.

Thanks.

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

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 31286 <at> debbugs.gnu.org
Subject: Re: bug#31286: 26.1; edebug prevents closing
Date: Fri, 27 Apr 2018 15:46:08 +0200

On 27.04.2018 10:46, Eli Zaretskii wrote:
>> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
>> Date: Fri, 27 Apr 2018 10:24:57 +0200
>>
>> Hi, this is a very old issue, don't see it at https://debbugs.gnu.org/:
>>
>> when closing a file where a function was instrumented running edebug,
>> Emacs refuses to get shut down afterwards. After answering the common
>> closing questionaire, a buffer appears again and again showing
>>
>> Debugger entered: nil
>>     edebug--display-1(nil 0 before)
>>     edebug--display(nil 0 before)
>>     edebug-debugger(0 before nil)
>>     edebug-before(0)
>>     ...
>>
>> and thats it.
> 
> I can reproduce this only partially.  After killing the buffer that
> visits the file whose function was instrumented using edebug-defun, I
> indeed see an error and a backtrace when I invoke a command which
> calls that function.  But I have no problem shutting down Emacs,
> either before or after the backtrace pops up.
> 
> So I'm guessing some other customization of yours is involved; please
> try in "emacs -Q" to see if your observations are different from mine.
> 
> If you can reproduce this starting with "emacs -Q", please show a
> recipe.
> 
> Thanks.
> 


Hmm, currently can't reproduce it any more - whether from emacs -Q or 
not. Maybe close it for now. As running into this from time to time, 
I'll try to be more vigilant WRT cause.

Thanks,

Andreas

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 31286-done <at> debbugs.gnu.org
Subject: Re: bug#31286: 26.1; edebug prevents closing
Date: Fri, 27 Apr 2018 17:16:25 +0300

> Cc: 31286 <at> debbugs.gnu.org
> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
> Date: Fri, 27 Apr 2018 15:46:08 +0200
> 
> Hmm, currently can't reproduce it any more - whether from emacs -Q or 
> not. Maybe close it for now.

Done, thanks.

Previous Next

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