This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
MI output command error
- From: Bob Rossi <bob at brasko dot net>
- To: GDB <gdb at sources dot redhat dot com>
- Date: Tue, 8 Mar 2005 21:39:57 -0500
- Subject: MI output command error
Hi,
The doco for -break-watch has,
(gdb)
-break-watch x
^done,wpt={number="2",exp="x"}
(gdb)
-exec-continue
^running
^done,reason="watchpoint-trigger",wpt={number="2",exp="x"},
value={old="-268439212",new="55"},
frame={func="main",args=[],file="recursive2.c",line="5"}
(gdb)
However, when I run it with GDB from CVS, I get,
(gdb)
-break-watch argc
^done,wpt={number="2",exp="argc"}
(gdb)
-exec-continue
^running
(gdb)
*stopped,reason="watchpoint-scope",wpnum="2",thread-id="0",frame={addr="0x40039dc9",func="__libc_start_main",args=[],from="/lib/libc.so.6"}
(gdb)
The problem is, the -exec-continue command in CVS has an extra '(gdb)'
in it after '^running'. I don't know if the doco or GDB is correct.
I do know that I think GDB is conforming to the MI output command
syntax, even though I think the documentation output looks more correct.
Was the extra "(gdb)" added to make the output command match the syntax?
Is this a bug in the doco or in GDB?
Thanks,
Bob Rossi