This is the mail archive of the 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: [PATCH] -stack-info-frame/-stack-list-frames

On Wed, Apr 23, 2008 at 06:24:14PM -0400, Daniel Jacobowitz wrote:
> On Thu, Apr 24, 2008 at 10:15:07AM +1200, Nick Roberts wrote:
> > But thats a good cas in point.  If the frontend end is to operate in a
> > stateless manner, as Vladimir has suggested, and varobjs are created in
> > non-selected frames, it needs to know the frame addresses:
> > 
> > -var-create - FRAME-ADDR EXPRESSION
> No, it doesn't.  We need to kill that interface.  It needs to go away.
> You gave a perfect example in your other reply, just now, of why front
> ends should not have a frame address.  If you are ever in the position
> of dealing with a recursive function and you want to know which
> instance a variable comes from, the frame address is insufficient.
> For instance IA-64 can have stackless recursive functions; they
> use only the separate register stack.
> If you want to know which frame the varobj is associated with GDB
> should supply some unique opaque identifier, and then the IDE can
> use that to show the frame number in a tooltip or wherever.

I've got a good idea, how about the frame number?

Bob Rossi

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