unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* edebug question - context of calling function
@ 2003-10-15  7:18 David Vanderschel
       [not found] ` <mailman.1841.1066353965.21628.help-gnu-emacs@gnu.org>
  2003-10-17 18:35 ` jan
  0 siblings, 2 replies; 9+ messages in thread
From: David Vanderschel @ 2003-10-15  7:18 UTC (permalink / raw)


I sometimes put a source breakpoint in my code to
catch a particular error condition.  When such a
conditional breakpoint fires, the actual problem,
though recognized in the called function, is often
attributable to the calling function.  What I want to
do then is to look around at the state of the calling
function at the time it called the function which
invoked edebug.  I can instrument the calling
function; but, when in the debugger, I cannot see how
to pop the context stack so that I can look around at
the variables in the calling program.  What am I
missing?

Thanks,
  David V.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2003-10-30  3:38 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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).