From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Problems with debug-on-entry in the Lisp debugger. Date: Mon, 07 Mar 2005 21:53:03 -0500 Message-ID: References: <87sm37n2bv.fsf@xs4all.nl> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1110251049 23173 80.91.229.2 (8 Mar 2005 03:04:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2005 03:04:09 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 08 04:04:08 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D8V0r-0007OC-Cw for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2005 04:04:01 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D8VFF-00087C-LB for ged-emacs-devel@m.gmane.org; Mon, 07 Mar 2005 22:18:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D8VEJ-0007hS-2c for emacs-devel@gnu.org; Mon, 07 Mar 2005 22:17:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D8VEB-0007bJ-L1 for emacs-devel@gnu.org; Mon, 07 Mar 2005 22:17:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D8VE6-0007WN-Vx for emacs-devel@gnu.org; Mon, 07 Mar 2005 22:17:43 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D8UqF-0008BG-Ge for emacs-devel@gnu.org; Mon, 07 Mar 2005 21:53:03 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D8UqF-0008L2-76; Mon, 07 Mar 2005 21:53:03 -0500 Original-To: Lute Kamstra In-reply-to: <87sm37n2bv.fsf@xs4all.nl> (message from Lute Kamstra on Mon, 07 Mar 2005 12:05:24 +0100) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34302 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34302 The only solution (within the current implementation) that I can think of, is to temporarily remove all debug-on-entry code while stepping with `d'. Would setting inhibit-debug-on-entry temporarily do the job? I can think of two points in a macro to set a break for the debugger: just before macro expansion and just after it, right before the evaluation of the resulting sexp. The correct place to do it is before macro expansion. This is a very evident bug, so please just fix it if you can. In both cases, hiding the debug-on-entry code from the user of the debugger seems not possible. I am not sure what that means. When I was thinking about these three problems, it seemed to me that the easiest and simplest thing to do, is to move support for debug-on-entry into the C implementation of the Lisp interpreter. To mark a function for debug-on-entry, you could set the debug-on-entry property of the function's symbol and the Lisp interpreter would then call the debugger. I agree this is undesirable due to slowness. I don't see a need for this big a change.