From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31286@debbugs.gnu.org
Subject: bug#31286: 26.1; edebug prevents closing
Date: Fri, 27 Apr 2018 15:46:08 +0200 [thread overview]
Message-ID: <2be4338a-2a0a-9bef-1648-e72ffd11c2b0@easy-emacs.de> (raw)
In-Reply-To: <83604dujdt.fsf@gnu.org>
On 27.04.2018 10:46, Eli Zaretskii wrote:
>> From: Andreas Röhler <andreas.roehler@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
next prev parent reply other threads:[~2018-04-27 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:24 bug#31286: 26.1; edebug prevents closing Andreas Röhler
2018-04-27 8:46 ` Eli Zaretskii
2018-04-27 13:46 ` Andreas Röhler [this message]
2018-04-27 14:16 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2be4338a-2a0a-9bef-1648-e72ffd11c2b0@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=31286@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).