From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "David Vanderschel" Newsgroups: gmane.emacs.help Subject: edebug question - context of calling function Date: Wed, 15 Oct 2003 02:18:11 -0500 Organization: hardly ever ;-) Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1066203310 30257 80.91.224.253 (15 Oct 2003 07:35:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2003 07:35:10 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 15 09:35:07 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 1A9gBX-0005Le-00 for ; Wed, 15 Oct 2003 09:35:07 +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 1A9g7L-0004Bw-P7 for geh-help-gnu-emacs@m.gmane.org; Wed, 15 Oct 2003 03:30:47 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!elnk-pas-nf1!newsfeed.earthlink.net!small1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!intern1.nntp.aus1.giganews.com!nntp.giganews.com!nntp.texas.net!news.texas.net.POSTED!not-for-mail Original-NNTP-Posting-Date: Wed, 15 Oct 2003 02:18:08 -0500 Original-Newsgroups: gnu.emacs.help X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Original-Lines: 17 Original-X-Trace: sv3-rct/qjIvB5PshnDPET685NMlUvTyXWccul2KdEZa6jzzT+nz0Fj44+gEWdivevdqIp2/y7cjmjwIJdP!O/yVW9vS/8VFJfh/DGLMC0axtFLTmFuE1kNEjxyfcV9Y0xYQPG3q1oDncImt Original-X-Complaints-To: abuse@texas.net X-DMCA-Complaints-To: abuse@texas.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 Original-Xref: shelby.stanford.edu gnu.emacs.help:117261 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:13190 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:13190 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.