From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: edebug question - context of calling function Date: Fri, 24 Oct 2003 15:51:45 GMT Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: <0tWdnZ-zD5A5zBKiRTvUqg@texas.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1067011383 13911 80.91.224.253 (24 Oct 2003 16:03:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 24 Oct 2003 16:03:03 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Oct 24 18:03:01 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AD4Oy-0006KG-01 for ; Fri, 24 Oct 2003 18:03:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AD4On-0005Ik-OJ for geh-help-gnu-emacs@m.gmane.org; Fri, 24 Oct 2003 12:02:49 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!nntp.cs.ubc.ca!cyclone.bc.net!snoopy.risq.qc.ca!charlie.risq.qc.ca!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-NNTP-Posting-Host: 132.204.24.42 Original-X-Complaints-To: abuse@umontreal.ca Original-X-Trace: charlie.risq.qc.ca 1067010705 132.204.24.42 (Fri, 24 Oct 2003 11:51:45 EDT) Original-NNTP-Posting-Date: Fri, 24 Oct 2003 11:51:45 EDT Original-Xref: shelby.stanford.edu gnu.emacs.help:117586 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 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 Xref: main.gmane.org gmane.emacs.help:13518 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:13518 [ I haven't seen the earlier part of the thread. ] > I am familiar with other debuggers which allow you to > proceed up and down the stack of call frames, looking > at context (including location of the call in each > calling program) in a whole hierarchy of calling > functions. I just expected such capability in edebug > and was trying to find out how to exercise it. > However, I am willing to accept that the capability is > not there. I don't think edebug has that feature, although I can't think of any particular reason why not (as long as the calling function you want to look at is instrumented, of course). If your calling function is byte-compiled, you can improve things a little by using the non-byte-compiled version in which case the backtrace will give you more than just the calling function's name and arguments. It won't give you line numbers, but you should/might be able to recognize the calling context enough to figure out which of the calls is currently active. Stefan