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: Re: edebug question - context of calling function Date: Thu, 16 Oct 2003 21:19:17 -0500 Organization: hardly ever ;-) Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <0tWdnZ-zD5A5zBKiRTvUqg@texas.net> References: NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1066357953 1357 80.91.224.253 (17 Oct 2003 02:32:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 17 Oct 2003 02:32:33 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Oct 17 04:32:30 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 1AAKPm-00007z-00 for ; Fri, 17 Oct 2003 04:32:30 +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 1AAKOI-00064q-Pz for geh-help-gnu-emacs@m.gmane.org; Thu, 16 Oct 2003 22:30:58 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!elnk-pas-nf1!newsfeed.earthlink.net!border2.nntp.ash.giganews.com!border1.nntp.ash.giganews.com!firehose2!nntp4!intern1.nntp.aus1.giganews.com!nntp.giganews.com!nntp.texas.net!news.texas.net.POSTED!not-for-mail Original-NNTP-Posting-Date: Thu, 16 Oct 2003 21:19:16 -0500 Original-Newsgroups: gnu.emacs.help X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Original-Lines: 37 Original-X-Trace: sv3-vsVRe3RxlR1+5w6ccBVlugNn+lHwqdINiuIMhafUpNE4JNvZ3dr5qX7HFejMN7NgoMQtsKMi7lQP0Gq!8QQ/b30MoIKPI6g/JiWUacQJnDie8GdVy84Bt2hyNHx0YmwK9SaeCqkmszcr 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:117347 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:13277 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:13277 "jan" wrote in message news:... > "David Vanderschel" writes: > > 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? > If I understand you correctly, you want to walk up the stack and look > at the local variable in the functions along the way. I had a quick > look and both edebug and the standard emacs debugger seem to be > missing this feature. However, it may not be necessary because elisp > is a dynamically scoped language, for example: I think you do understand me correctly. Unfortunately, I often reuse the same local variables (eg., i, j, x, ...). I was also interested in the calling context in the sense of "Among multiple possible invocations in the calling program, which invocation of of the function which noticed the condition caused this break." I guess you are correct that I have to move the logic which catches the inconsistency up a level. But there is no one nice place to put it for the bug I am chasing now. Regards, David V.