From: Andrew Cagney <ac131313@redhat.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testcase] gdb.base/bang.exp: accespt sim's output
Date: Mon, 07 Jul 2003 14:19:00 -0000 [thread overview]
Message-ID: <3F098189.2090601@redhat.com> (raw)
In-Reply-To: <011201c341d6$5c5d48d0$5169910a@KEI>
> The attached patch fixes gdb.base/bang.exp so that it accepts
> sim's output.
>
> The current test always fails with sim.
>
> (gdb) run
> Starting program:
> /project/m32r-tools/insight-20030703/build/gdb/testsuite/gdb.base/bang!
> 0
>
> *** EXIT code 0
This is from the test wrapper stuff? Now that the h8300 is fixed (exits
with proper exit codes), wouldn't it be better to instead just delete
the wrapper stuff from the test framework and make the h8300 a normal
target?
Andrew
> Program exited normally.
> [Switching to process 0]
> (gdb) FAIL: gdb.base/bang.exp: run program (the program exited)
next prev parent reply other threads:[~2003-07-07 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 2:43 Kei Sakamoto
2003-07-04 3:02 ` Kei Sakamoto
2003-07-07 14:19 ` Andrew Cagney [this message]
2003-07-07 18:09 ` Daniel Jacobowitz
2003-07-07 18:55 ` Andrew Cagney
2003-07-07 19:59 ` 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=3F098189.2090601@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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