This is the mail archive of the gdb@sources.redhat.com 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: How does GDB/MI give the current frame

From: Nick Roberts <nickrob at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>,Andrew Cagney <cagney at gnu dot org>
Cc: gdb at sources dot redhat dot com
Date: Sat, 26 Jun 2004 10:08:41 +0100
Subject: Re: How does GDB/MI give the current frame
References: <16603.23348.569889.284030@nick.uklinux.net><20040624231659.GA16577@nevyn.them.org>

Daniel Jacobowitz writes:
DJ> 
DJ> Why not use -stack-info-frame?

Because AFAIK this MI command has not been implemented (yet).

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.

Nick

Follow-Ups:
- Re: How does GDB/MI give the current frame
  - From: Daniel Jacobowitz
- Re: How does GDB/MI give the current frame
  - From: Andrew Cagney

References:
- How does GDB/MI give the current frame
  - From: Nick Roberts
- Re: How does GDB/MI give the current frame
  - From: Daniel Jacobowitz

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