From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.help Subject: Standard Elisp debugger vs. Edebug Date: Tue, 05 May 2015 23:52:14 +0200 Message-ID: <874mnqofox.fsf@mbork.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430862769 567 80.91.229.3 (5 May 2015 21:52:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 5 May 2015 21:52:49 +0000 (UTC) To: Help Gnu Emacs mailing list Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue May 05 23:52:42 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ypkle-0007WI-3q for geh-help-gnu-emacs@m.gmane.org; Tue, 05 May 2015 23:52:42 +0200 Original-Received: from localhost ([::1]:41748 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ypkld-0001nj-E2 for geh-help-gnu-emacs@m.gmane.org; Tue, 05 May 2015 17:52:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41698) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpklQ-0001lc-9l for help-gnu-emacs@gnu.org; Tue, 05 May 2015 17:52:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YpklN-0005P6-9T for help-gnu-emacs@gnu.org; Tue, 05 May 2015 17:52:28 -0400 Original-Received: from mail.mojserwer.eu ([2a01:5e00:2:52::8]:59647) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpklN-0005P2-2g for help-gnu-emacs@gnu.org; Tue, 05 May 2015 17:52:25 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 0AA8F4FA048 for ; Tue, 5 May 2015 23:52:23 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqkhohLr7dG0 for ; Tue, 5 May 2015 23:52:20 +0200 (CEST) Original-Received: from localhost (unknown [109.232.24.146]) by mail.mojserwer.eu (Postfix) with ESMTPSA id E4F694FA047 for ; Tue, 5 May 2015 23:52:19 +0200 (CEST) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:5e00:2:52::8 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:104226 Archived-At: Hi all, there are two Elisp debuggers built into Emacs: the "standard" debugger and Edebug. Edebug seems more powerful and easier to use. The obvious question arises: is there any reason to use the standard debugger at all? My gut feeling is that while Edebug is nicer to use and more powerful, there might be cases when it doesn't work. For once, it seems that there is no edebug-on-error option, and the only (?) way to use Edebug to locate/examine errors is to manually step to the place where an error occurs (or set up a breakpoint, temporary or otherwise, near the suspicious location). Even then, Edebug won't show me the backtrace, for instance, and edebugging complicated code (in case I don't know exactly where the error occurs) might be rather difficult/cumbersome. So, the standard debugger at least helps to locate the error, and then I can use Edebug to watch the code "live". Am I right? Another suspicion of mine is that the standard debugger is lower-level, and it might be the case that some code (e.g., macros) will trip edebug (since you have to use debug declarations in macro definitions - and what if you have bugs in these?). I would guess that using the standard debugger might be easier with macro-heavy code, at least sometimes. Am I right? Are there any other reasons to choose the standard debugger over Edebug? TIA, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University