From: Nick Roberts <nickrob@snap.net.nz>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: drow@false.org (Daniel Jacobowitz), gdb-patches@sourceware.org
Subject: Re: -var-create testsuite updates [PATCH]
Date: Fri, 09 Mar 2007 01:41:00 -0000 [thread overview]
Message-ID: <17904.47955.434664.273574@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200703090100.l29106BM024625@d12av02.megacenter.de.ibm.com>
> >! mi_gdb_test "-var-create lpcharacter * lpcharacter" \
> >! "\\^done,name=\"lpcharacter\",numchild=\"1\",value=\"$hex \\\\\".*\\\\\"\",type=\"char \\*\"" \
> >! "create local variable lpcharacter"
>
> I'm not completely sure what the somewhat complex regular expression after "value"
> is supposed to test, but it fails on SPU. I get:
>
> -var-create lpcharacter * lpcharacter^M
> ^done,name="lpcharacter",numchild="1",value="0x0",type="char *"^M
> (gdb) ^M
> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lpcharacter
>
> Is this a testcase problem, or is there really something going wrong?
The test is wrong. It looks like SPU initialises locals to 0.
> (B.t.w. the same problem occurs also in mi2-var-cmd.exp.)
The value field for -var-create is new. I tried to make the regexp as specific
as possible for a more exacting test.
If value=\"($hex).*\" works in all cases (I might have the syntax wrong,
I mean matching "0xabc" and "0xabc \"blah\"") that would be good. Otherwise
just value=\".*\" will do.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-03-09 1:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:20 -var-create testsuite updates Daniel Jacobowitz
2007-02-09 20:48 ` Nick Roberts
2007-02-09 20:57 ` Daniel Jacobowitz
2007-02-11 21:43 ` Nick Roberts
2007-02-11 21:46 ` Daniel Jacobowitz
2007-02-12 6:18 ` Vladimir Prus
2007-02-12 9:30 ` Nick Roberts
2007-02-13 12:03 ` Daniel Jacobowitz
2007-02-15 20:55 ` -var-create testsuite updates [PATCH] Nick Roberts
2007-02-27 17:10 ` Daniel Jacobowitz
2007-03-09 1:00 ` Ulrich Weigand
2007-03-09 1:41 ` Nick Roberts [this message]
2007-03-09 2:22 ` Ulrich Weigand
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=17904.47955.434664.273574@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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