From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Tests for the target description XML parser
Date: Thu, 08 Mar 2007 23:10:00 -0000 [thread overview]
Message-ID: <200703082309.l28N9tqG012916@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070123171403.GA18292@nevyn.them.org> from "Daniel Jacobowitz" at Jan 23, 2007 12:14:03 PM
Daniel Jacobowitz wrote:
> 2007-01-23 Daniel Jacobowitz <dan@codesourcery.com>
>
> * Makefile.in (ALL_SUBDIRS): Add gdb.xml.
> * configure: Regenerated.
> * configure.ac (AC_OUTPUT): Add gdb.xml/Makefile.
> * gdb.xml/Makefile.in, gdb.xml/tdesc-arch.exp,
> gdb.xml/tdesc-bogus.xml, gdb.xml/tdesc-errors.exp,
> gdb.xml/trivial.xml, gdb.xml/tdesc-unknown.xml: New files.
> * lib/gdb.exp (gdb_skip_xml_test): New function.
> Index: src/gdb/testsuite/gdb.xml/tdesc-arch.exp
> ===================================================================
> +# Find some valid architectures - we just need legitimate values
> +# to put in our <architecture> elements.
> +set arch1 ""
> +set arch2 ""
> +set msg "read valid architectures"
> +gdb_test_multiple "set architecture" $msg {
> + -re "Requires an argument. Valid arguments are (\[^ \]*), (\[^ \]*), .*auto\\.\r\n$gdb_prompt $" {
> + set arch1 $expect_out(1,string)
> + set arch2 $expect_out(2,string)
> + pass $msg
> + }
> +}
This causes a FAIL on spu, since the target supports only a
single architecture, and the pattern requires two. This
probably was not the intention?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-03-08 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 17:14 Daniel Jacobowitz
2007-03-08 23:10 ` Ulrich Weigand [this message]
2007-03-08 23:20 ` Daniel Jacobowitz
2007-03-09 0:05 ` Ulrich Weigand
2007-03-09 0:10 ` Daniel Jacobowitz
2007-03-09 0:14 ` 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=200703082309.l28N9tqG012916@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