This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
[GDB/MI] missing token in "stopped" output after -exec-run?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: gdb at sourceware dot org
- Date: Tue, 20 May 2008 20:59:24 -0700
- Subject: [GDB/MI] missing token in "stopped" output after -exec-run?
Hello,
I noticed what looks like a change of behavior in MI and I was wondering
if this was intended. From my limited understanding of MI, it does look
like a bug, but it's hard to be sure for someone who's not familiar with
this protocol.
Consider the following program:
int
main (void)
{
}
Compile it with:
% gcc -g -o foo foo.c
Then break on main, and run to the breakpoint. Make sure the -exec-run
command has a token. Here is a transcript of my session:
(gdb)
-break-insert -t main
^done,bkpt={number="1",type="breakpoint",disp="del",enabled="y",addr="0x08048332",func="main",file="foo.c",fullname="/home/no-backup/brobecke/head-merge/ex/foo.c",line="6",times="0",original-location="main"}
(gdb)
232-exec-run
232^running
(gdb)
=thread-created,id="1"
*stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x08048332",func="main",args=[],file="foo.c",fullname="/home/no-backup/brobecke/head-merge/ex/foo.c",line="6"}
A few weeks ago, the output looked like this:
232-exec-run
232^running
(gdb)
232*stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x08048332",func="main",args=[],file="foo.c",fullname="/home/no-backup/brobecke/head-merge/ex/foo.c",line="6"}
The token was preserved. Is the new behavior intended?
--
Joel