From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [mi] Some error path fixes
Date: Fri, 09 Mar 2007 01:16:00 -0000 [thread overview]
Message-ID: <200703090116.l291GC7g004447@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070309010238.GA5849@caradoc.them.org> from "Daniel Jacobowitz" at Mar 08, 2007 08:02:38 PM
Daniel Jacobowitz wrote:
> I think you're right - the braces should be removed.
OK, I've committed the following patch, which fixes the
test case on spu-elf. Thanks!
Bye,
Ulrich
ChangeLog:
* gdb.mi/mi-var-cmd.exp: Allow -var-update null_ptr test to
pass on targets where address zero is readable.
Index: gdb/testsuite/gdb.mi/mi-var-cmd.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-var-cmd.exp,v
retrieving revision 1.27
diff -u -p -r1.27 mi-var-cmd.exp
--- gdb/testsuite/gdb.mi/mi-var-cmd.exp 28 Feb 2007 17:32:51 -0000 1.27
+++ gdb/testsuite/gdb.mi/mi-var-cmd.exp 9 Mar 2007 01:11:37 -0000
@@ -603,7 +603,7 @@ mi_gdb_test "-var-create null_ptr * **0"
# will not test what it was meant to. Most important is that GDB
# does not crash.
mi_gdb_test "-var-update null_ptr" \
- {\^done,changelist=\[{.*}\]} \
+ {\^done,changelist=\[.*\]} \
"update null_ptr"
mi_gdb_test "-var-delete null_ptr" \
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-03-09 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:00 Daniel Jacobowitz
2007-01-04 21:59 ` Daniel Jacobowitz
2007-03-09 0:55 ` Ulrich Weigand
2007-03-09 1:02 ` Daniel Jacobowitz
2007-03-09 1:16 ` Ulrich Weigand [this message]
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=200703090116.l291GC7g004447@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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