From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Problems with debug-on-entry in the Lisp debugger.
Date: Wed, 09 Mar 2005 11:58:42 -0500
Message-ID: <E1D94WA-00065w-0x@fencepost.gnu.org>
References: <87sm37n2bv.fsf@xs4all.nl> <E1D8UqF-0008L2-76@fencepost.gnu.org>
	<87is42c8yp.fsf@xs4all.nl>
Reply-To: rms@gnu.org
NNTP-Posting-Host: main.gmane.org
X-Trace: sea.gmane.org 1110388346 24540 80.91.229.2 (9 Mar 2005 17:12:26 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Wed, 9 Mar 2005 17:12:26 +0000 (UTC)
Cc: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 18:12:25 2005
Original-Received: from lists.gnu.org ([199.232.76.165])
	by ciao.gmane.org with esmtp (Exim 4.43)
	id 1D94eh-0006y4-BW
	for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2005 18:07:32 +0100
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1D94tP-00029r-AL
	for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2005 12:22:43 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1D94rb-00011i-2B
	for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:51 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1D94rW-0000zx-5f
	for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:48 -0500
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1D94rV-0000p0-Fv
	for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:45 -0500
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1D94WA-0000dZ-Bg
	for emacs-devel@gnu.org; Wed, 09 Mar 2005 11:58:42 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34)
	id 1D94WA-00065w-0x; Wed, 09 Mar 2005 11:58:42 -0500
Original-To: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
In-reply-to: <87is42c8yp.fsf@xs4all.nl> (message from Lute Kamstra on Tue, 08
	Mar 2005 19:02:06 +0100)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=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:34380
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34380

      Temporary setting debugger-jumping-flag
    would solve the problem of stepping into the code of the debugger.
    (I'll implement this fix.)

Thanks.

				The debug-entry-code would still be
    visible in the backtrace however.

That is not a problem.  It might even help users learn to understand
that programs are data.