From: Daniel Jacobowitz <drow@false.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: Possibly dumb signal mapping question
Date: Fri, 18 Mar 2005 14:53:00 -0000 [thread overview]
Message-ID: <20050318145234.GA24185@nevyn.them.org> (raw)
In-Reply-To: <423AE9EF.2070401@qnx.com>
On Fri, Mar 18, 2005 at 09:47:11AM -0500, Kris Warkentin wrote:
> Daniel Jacobowitz wrote:
>
> >Your stub should be doing this. The TARGET_SIGNAL_* constants are the
> >on-the-wire values.
> >
>
> Thanks Daniel. I guess I've got to do it the hard way. I had just
> asked because I thought there might be some magic mapping routine like
> for the i386 registers.
No, there isn't - you could do it in your remote protocol target (don't you
use a different protocol?)
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-18 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:30 Kris Warkentin
2005-03-17 22:33 ` Daniel Jacobowitz
2005-03-18 14:47 ` Kris Warkentin
2005-03-18 14:53 ` Daniel Jacobowitz [this message]
2005-03-18 15:00 ` Kris Warkentin
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=20050318145234.GA24185@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).