Re: edebug question - context of calling function

[Stefan Monnier]

[ 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