public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: nrun: decode signal when crashing
Date: Tue, 16 Nov 2010 19:06:00 -0000	[thread overview]
Message-ID: <201011161404.56309.vapier@gentoo.org> (raw)
In-Reply-To: <y0m62vxw8os.fsf@fche.csb>

[-- Attachment #1: Type: Text/Plain, Size: 1248 bytes --]

On Tuesday, November 16, 2010 11:10:43 Frank Ch. Eigler wrote:
> vapier wrote:
> > [...]
> > 
> >        if (sigrc != 0)
> > 
> > -        fprintf (stderr, "program stopped with signal %d.\n", sigrc);
> > +	fprintf (stderr, "program stopped with signal %d (%s).\n", sigrc,
> > +		 strsignal (sigrc));
> > 
> >        break;
> 
> I don't know if we can assume that the target signal numbering matches
> the host.  Else I suspect we wouldn't have all those TARGET_SIGNAL_*
> defs.

for the platforms i care about, they are ;).  but that's a fair point.  i 
think the reason i did this is because the signal_map logic isnt really used 
anywhere that i can see.  perhaps i should bite the bullet and add a 
target_strsignal() that operates on the callback maps ...

i get the feeling that the sim history is something like:
 - there were no viable sims, so this one was started up ... it was a bit 
bare, but it worked for people's minimal needs
 - ibm threw a lot of money at developers who created a pretty full ppc sim as 
a semi-fork ... then over time, much of that work was merged back
 - qemu gathered steam and sucked up all the potential developers
 - many cool sim features remain stalled & under developed
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-11-16 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  2:50 Mike Frysinger
2010-11-16 16:10 ` Frank Ch. Eigler
2010-11-16 19:06   ` Mike Frysinger [this message]
2010-12-28  4:43   ` Mike Frysinger
2012-03-19  3:59     ` 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=201011161404.56309.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=fche@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).