unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: How to stop all edebug?
Date: Wed, 23 Oct 2019 08:43:09 -0400	[thread overview]
Message-ID: <jwvzhhrljod.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: KL1PR0601MB36532871BE02956CB945EF3EA86B0@KL1PR0601MB3653.apcprd06.prod.outlook.com

> I edebug(use edebug-defun) some functions in file.el and then close
> file.el. When I open a new file, emacs aborts and show a buffer with edebug
> error(It can’t find the original buffer to debug).
>
> And I event can’t quit emacs because there are functions in kill-emacs-hook
> which try to open file and save data(such as recentf).

Could you make a bug report for that?

If the source buffer is not available any more (as in your case above),
it's OK for Edebug to complain loudly, but it shouldn't prevent you from
using Emacs normally enough to exit or restore sanity.

E.g. after "aborts and show a buffer with edebug error" it could/should
offer to either cancel the "edebug on entry" or to de-instrument the function.


        Stefan




  parent reply	other threads:[~2019-10-23 12:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:56 How to stop all edebug? Zhang Haijun
2019-10-23  6:46 ` Michael Heerdegen
     [not found]   ` <mailman.1523.1571813205.9715.help-gnu-emacs@gnu.org>
2019-10-23  7:31     ` Lars Magne Ingebrigtsen
2019-10-24 11:09       ` Michael Heerdegen
2019-10-24  4:10   ` HaiJun Zhang
2019-10-24 11:05     ` Michael Heerdegen
2019-10-24 12:45       ` HaiJun Zhang
2019-10-24 13:13         ` Michael Heerdegen
2019-10-24 14:10           ` HaiJun Zhang
     [not found]       ` <70a705e7-cebf-4ac4-b7af-0fc04b383de6@Spark>
2019-10-24 13:12         ` HaiJun Zhang
2019-10-23 12:43 ` Stefan Monnier [this message]
2019-10-24  4:12   ` HaiJun Zhang
2019-10-23 15:21 ` Eli Zaretskii
2019-10-24  4:16   ` HaiJun Zhang

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=jwvzhhrljod.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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. 
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).