From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: edebug question - context of calling function
Date: Fri, 24 Oct 2003 15:51:45 GMT [thread overview]
Message-ID: <jwvu15yskro.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: P5GdnXn7D8eRhQSiRTvUrg@texas.net
[ 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
next prev parent reply other threads:[~2003-10-24 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 7:18 edebug question - context of calling function David Vanderschel
[not found] ` <mailman.1841.1066353965.21628.help-gnu-emacs@gnu.org>
2003-10-17 2:19 ` David Vanderschel
2003-10-18 19:59 ` jan
[not found] ` <mailman.1915.1066445382.21628.help-gnu-emacs@gnu.org>
2003-10-24 12:16 ` David Vanderschel
2003-10-24 15:51 ` Stefan Monnier [this message]
2003-10-24 18:41 ` David Vanderschel
2003-10-26 3:13 ` jan
[not found] ` <mailman.2431.1067076191.21628.help-gnu-emacs@gnu.org>
2003-10-30 3:38 ` David Vanderschel
2003-10-17 18:35 ` jan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvu15yskro.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).