From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>,
Corinna Vinschen <vinschen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.base/bang.exp: Allow trailing text after "Program exited normally"
Date: Mon, 08 Sep 2003 18:52:00 -0000 [thread overview]
Message-ID: <3F5CCFEC.4090007@redhat.com> (raw)
In-Reply-To: <20030908132716.GA17563@nevyn.them.org>
> On Mon, Sep 08, 2003 at 01:42:01PM +0200, Corinna Vinschen wrote:
>
>> Hi,
>>
>> while testing I found that a test for ending the program in
>> gdb.base/bang.exp failed, even though the target had actually
>> exited normally. The cause of the FAIL is that bang.exp doesn't
>> expect anything after the string "Program exited normally.".
>> On the sh target at least, the output after exiting contains a
>> bit more text:
>>
>> Program exited normally.
>> [Switching to process 0]
>>
>> Since that trailing output after a normal exit doesn't change
>> anything with respect to the testresult, I propose to allow
>> trailing characters:
>
>
> But isn't the [Switching to process 0] a bug? We aren't switching
> processes, the inferior is dead.
Yes. The message is both a bug and a very long standing regression.
Andrew
PS: Suggest a reminder comment that SIGNALED is really "terminated with
signal" :-)
next prev parent reply other threads:[~2003-09-08 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 11:42 Corinna Vinschen
2003-09-08 13:27 ` Daniel Jacobowitz
2003-09-08 14:30 ` Corinna Vinschen
2003-09-08 14:52 ` Daniel Jacobowitz
2003-09-08 15:39 ` Corinna Vinschen
2003-09-08 18:52 ` Andrew Cagney [this message]
2003-09-08 20:14 ` 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=3F5CCFEC.4090007@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@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