From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: gdb-patches@sourceware.org
Subject: Re: Please fix regressions from your sim changes
Date: Mon, 19 Mar 2012 23:51:00 -0000 [thread overview]
Message-ID: <201203192350.q2JNogb6032347@ignucius.se.axis.com> (raw)
In-Reply-To: <201203191322.40953.vapier@gentoo.org> (message from Mike Frysinger on Mon, 19 Mar 2012 18:22:39 +0100)
> From: Mike Frysinger <vapier@gentoo.org>
> Date: Mon, 19 Mar 2012 18:22:39 +0100
(CC to the list disappeared much like the test-case output,
sorry Mike for getting this twice.)
> On Monday 19 March 2012 02:28:49 Hans-Peter Nilsson wrote:
> > For mips-elf, there's just
>
> mips-elf is passing for me
> > FAIL: mips1 hilo-hazard-1.s (execution)
>
> the glob should eat the new signal string
>
> > For cris-elf, there's quite a bit more, three variants AFAICT;
> > three "signals" lost.
>
> patch attached should fix that
>
> > And really, why removing the "program stopped with signal"
> > common part? I see no reason to not just adding it back.
>
> it wasn't removed. the signal is now additionally being decoded.
>
> before: program stopped with signal 5.
> after: program stopped with signal 5 (Trace/breakpoint trap).
That's what you'd think (and that'd be an improvement), but the
message really is all gone. Is it a host issue? The tester
host is admittedly an aging installation, F 8 x86_64.
brgds, H-P
next prev parent reply other threads:[~2012-03-19 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 6:29 Hans-Peter Nilsson
2012-03-19 17:23 ` Mike Frysinger
2012-03-19 23:51 ` Hans-Peter Nilsson [this message]
2012-03-20 2:30 ` Mike Frysinger
2012-03-20 5:55 ` Hans-Peter Nilsson
2012-03-20 16:16 ` Mike Frysinger
2012-03-20 16:30 ` Hans-Peter Nilsson
2012-03-23 4:23 ` Mike Frysinger
2012-03-21 4:49 ` Mike Frysinger
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=201203192350.q2JNogb6032347@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--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