This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: -var-update and address changes

From: Nick Roberts <nickrob at snap dot net dot nz>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Vladimir Prus <ghost at cs dot msu dot su>, Jim Ingham <jingham at apple dot com>, gdb at sources dot redhat dot com
Date: Sun, 16 Apr 2006 23:38:46 +1200
Subject: Re: -var-update and address changes
References: <e1iqcl$2k4$1@sea.gmane.org> <1A00C3C1-BDF5-489E-A36A-A1E5C20E102A@apple.com> <20060414131549.GC12955@nevyn.them.org>

 > > Can somebody suggest the right fix? So far, I think that the simplest
 > > approach is to make gdb print stack address of current frame, like is done
 > > on the Apple branch:
 > > 
 > >      553^done,stack=[frame= 
 > >      {level="0",addr="0x00003db0",fp="0xbffff2c0",......
 > > 
 > > That way, frontend can deal with the issue of frame stacks themself, and
 > > -var-update will be only used when single-stepping inside a given frame.
 > > Will patches to implement this be welcome?
 > 
 > I guess.  It seems reasonable.

ISTR that Totalview displays the fp address of each frame in the call stack.
This seems natural and I wonder why "info stack" chooses to display the pc
addresses.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

References:
- -var-update and address changes
  - From: Vladimir Prus
- Re: -var-update and address changes
  - From: Jim Ingham
- Re: -var-update and address changes
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]