This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [MI/RFC] Emit ^running via observer.
On Thu, Jun 26, 2008 at 07:58:05PM +0400, Vladimir Prus wrote:
> On Thursday 26 June 2008 07:20:14 Nick Roberts wrote:
> > > I've checked in the following, which differs from original by extra test
> > > strictness.
> >
> > Thanks.
> >
> > > Further, I've converted mi-async.exp to use the helper
> > > functions. Nick, as it stands now it does not seem that mi-async.exp tests
> > > async behaviour at all -- it merely changes that we get ^running for CLI
> > > commands, and we get that in both sync and async mode. Do you think it
> > > worthwhile to rename the test or move its content somewhere else?
> >
> > The tests appear to fail now.
>
> Which tests? With unmodified CVS state, all MI tests pass for me both in sync
> and async mode. But indeed, if I make mi-async.exp not force async mode, it
> starts to fail....
Not for me.
(gdb)
start
&"start\n"
~"Temporary breakpoint 1 at 0x400635: file /space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c, line 62.\n"
~"Starting program: /space/fsf/x86-64/commit-gdb/gdb/testsuite/gdb.mi/basics \n"
=thread-created,id="1"
^running
*running,thread-id="all"
*stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x0000000000400635",func="main",args=[],file="/space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c",fullname="/space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c",line="62"}
FAIL: gdb.mi/mi-async.exp: start: send
mi_expect_stop: expecting: \*stopped,reason="breakpoint-hit",disp="del",bkptno="[0-9]+",thread-id="[0-9]+",frame={addr="0x[0-9A-Fa-f]+",func="main",args=\[\],file=".*.*basics.c",fullname="(/.*/|\\\\[^\\]+\\.+\\|\\[^\\].*\\|[a-zA-Z]:.*\\).*basics.c",line="62"}
$
PASS: gdb.mi/mi-async.exp: start: stop
--
Daniel Jacobowitz
CodeSourcery