This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: FAILs on x86?
On Thursday 27 March 2008 16:51:07 you wrote:
>
> Vladimir Prus schrieb:
> > Then, I need gdb.log part for the first failure, namely this:
> >
> > FAIL: gdb.mi/gdb701.exp: create fooPtr
>
> Is this the correct snippet? Let me know if you want other parts. I can send you the whole file
> to your email address if you want to.
>
> 220-exec-next
>
> 220^running
>
> (gdb)
>
> 220*stopped,reason="end-stepping-range",thread-id="0",frame={addr="0x0804839c",func="main",args=[],file="/home/deuling/gdb/dev/gdb/testsuite/gdb.mi/gdb701.c",fullname="/home/deuling/gdb/dev/gdb/testsuite/gdb.mi/gdb701.c",line="14"}
>
> (gdb)
>
> PASS: gdb.mi/gdb701.exp: step over "foo = 0"
> -var-create fooPtr * foo
>
> ^done,name="fooPtr",numchild="3",type="Foo *"
>
> (gdb)
I assume the extra newlines appeared during posting. Anyway, the output is somewhat
"interesting". The test passes for me, and I get:
^done,name="fooPtr",numchild="3",value="0x0",type="Foo *",thread-id="1"
Note the "value" field that the test actually expects to find. Note also the thread-id
field that I believe should always be present on x86 these days. Are you sure you're
testing the right version of GDB?
- Volodya