From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: Getting stack traces without entering the debugger Date: Wed, 19 Feb 2014 18:13:11 +0100 Message-ID: <87bny33u1k.fsf@web.de> References: <87ob23qdyj.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392830037 14821 80.91.229.3 (19 Feb 2014 17:13:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Feb 2014 17:13:57 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Feb 19 18:14:03 2014 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 1WGAiZ-0006bl-OB for geh-help-gnu-emacs@m.gmane.org; Wed, 19 Feb 2014 18:13:55 +0100 Original-Received: from localhost ([::1]:60869 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGAiZ-0000fU-2d for geh-help-gnu-emacs@m.gmane.org; Wed, 19 Feb 2014 12:13:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGAiF-0000e5-Nj for help-gnu-emacs@gnu.org; Wed, 19 Feb 2014 12:13:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGAi8-0003kp-E0 for help-gnu-emacs@gnu.org; Wed, 19 Feb 2014 12:13:35 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:55773) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGAi8-0003kZ-7R for help-gnu-emacs@gnu.org; Wed, 19 Feb 2014 12:13:28 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WGAi6-0005lt-AP for help-gnu-emacs@gnu.org; Wed, 19 Feb 2014 18:13:26 +0100 Original-Received: from ip-90-186-56-226.web.vodafone.de ([90.186.56.226]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Feb 2014 18:13:26 +0100 Original-Received: from michael_heerdegen by ip-90-186-56-226.web.vodafone.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Feb 2014 18:13:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip-90-186-56-226.web.vodafone.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:c7ztYg8sU8wZa1PuCDSwuKLd0Ds= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:96125 Archived-At: E Sabof writes: > I'm trying to investigate an isearch-related issue, where a function > gets called twice, instead of once. Why don't you just `debug-on-entry' that function? > Is there a way to get a stack trace and save it to a variable, without > calling the debugger? You can use `backtrace' (which is actually called by the debugger to fill the *Backtrace* buffer) and use some temp buffer as `standard-output'. In recent Emacs version, there's also `macroexp--backtrace', a little helper in macroexp.el that returns a backtrace as a lisp expression. Even in older version, the simple definition should still work: (defun macroexp--backtrace () "Return the Elisp backtrace, more recent frames first." (let ((bt ()) (i 0)) (while (let ((frame (backtrace-frame i))) (when frame (push frame bt) (setq i (1+ i))))) (nreverse bt))) Unlike `backtrace', the result is complete, there are no parts that are replaced with ellipses by the printer. Of course, parts can still be omitted when you print the result. `pp' should work fine. The doc of `backtrace-frame' describes the format of the backtrace frames returned. Michael.