This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: MI testsuite to use PTY for inferior
- From: Bob Rossi <bob at brasko dot net>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Thu, 1 Sep 2005 19:51:48 -0400
- Subject: Re: MI testsuite to use PTY for inferior
- References: <20050727031758.GA15798@white> <200508132151.j7DLpnoR015475@elgar.sibelius.xs4all.nl> <20050819222721.GA20029@white> <20050830025203.GA16646@nevyn.them.org> <20050901005200.GA6990@white> <200509012211.j81MBfX1004484@elgar.sibelius.xs4all.nl>
> Fixes the problems in mi-console.exp, but I still see the following:
>
> 403-exec-continue
> 403^running
> (gdb)
> FAIL: gdb.mi/mi-syn-frame.exp: testing exec continue
> 403*stopped
> (gdb)
> 404-stack-list-frames 0 0
> 404^done,stack=[frame={level="0",addr="0x1c0006c8",func="main",file="../../../..
> /src/gdb/gdb/testsuite/gdb.mi/mi-syn-frame.c",fullname="/home/kettenis/src/gdb/g
> db/testsuite/gdb.mi/mi-syn-frame.c",line="14"}]
> (gdb)
> PASS: gdb.mi/mi-syn-frame.exp: list stack frames
>
> Seems the attached patch solves those though.
>
> Mark
O, great find Mark! I couldn't reproduce this, but now I see why the
testcase is failing. It's also a case where multiple MI output commands
were being matched in a single mi_gdb_test command.
I wonder how my changes effected the testsuite to cause these problems?
I'll take a look.
Thanks a lot!
Bob Rossi