From: Vladimir Prus <ghost@cs.msu.su>
To: Markus Deuling <deuling@de.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: FAILs on x86?
Date: Thu, 27 Mar 2008 14:19:00 -0000 [thread overview]
Message-ID: <200803271717.02355.ghost@cs.msu.su> (raw)
In-Reply-To: <47EBA64B.20209@de.ibm.com>
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
next prev parent reply other threads:[~2008-03-27 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 11:37 Markus Deuling
2008-03-27 11:51 ` Daniel Jacobowitz
2008-03-27 12:15 ` Markus Deuling
2008-03-27 12:23 ` Vladimir Prus
2008-03-27 12:33 ` Markus Deuling
2008-03-27 12:55 ` Vladimir Prus
2008-03-27 13:29 ` Markus Deuling
2008-03-27 13:40 ` Vladimir Prus
2008-03-27 13:51 ` Markus Deuling
2008-03-27 14:19 ` Vladimir Prus [this message]
2008-03-27 12:44 ` Daniel Jacobowitz
2008-03-27 12:48 ` Markus Deuling
2008-03-27 13:04 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803271717.02355.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox