How does GDB/MI give the current frame

Daniel Jacobowitz drow@false.org
Sat Jun 26 14:59:00 GMT 2004


On Sat, Jun 26, 2004 at 10:08:41AM +0100, Nick Roberts wrote:
> 
> Daniel Jacobowitz writes:
> DJ> 
> DJ> Why not use -stack-info-frame?
> 
> Because AFAIK this MI command has not been implemented (yet).

So it hasn't!  Silly me, I was fooled by it being documented in the
manual.

> Andrew Cagney writes:
> 
> AC> When the user does "up", "down", the debugger should generate a selected 
> AC> CLI frame changed event (it currently doesn't).  If the GUI so chooses, 
> AC> it can track the users "selected" frame, by responding to these events.
> 
> I don't know what a selected CLI frame changed event is but up, down, and
> frame generate MI output, so I imagine its just a case of hooking
> -stack-info-frame and -stack-select-frame to that output. I will try to do
> this if you think it's appropriate.

I think that Andrew's answering a related question: for debuggers which
allow entry of console commands, the interface needs a way to update
its windows when the user types "up".  Since you're just interested in
MI at the moment, I suspect that filling in -stack-info-frame is the
way to go.

I'm not sure whether -stack-select-frame should have output or not.

-- 
Daniel Jacobowitz



More information about the Gdb mailing list