From: Kris Warkentin <kewarken@qnx.com>
To: GDB <gdb@sources.redhat.com>
Subject: Possibly dumb signal mapping question
Date: Thu, 17 Mar 2005 22:30:00 -0000 [thread overview]
Message-ID: <4239F328.5000505@qnx.com> (raw)
Say I'm building a gdb on Linux that remotely targets Neutrino, what is
the acceptable way to map our OS signals onto TARGET_SIGNAL_*? I'm
looking at the target_signal_[to/from]_host functions but they look like
they depend on the various SIG*s having been defined. Wouldn't those
defines collide with host defines? Perhaps I'm getting confused for no
good reason.... If I _were_ going to define them, what would be a good
place?
I accidentally dropped the signal mapping code from our old port but in
looking at it, it looks too hacky to live. We've got some ugly
target_signal_[to/from]_qnx functions that we just use to convert any
signals sent to and from the remote target. Is there a better way?
cheers,
Kris
next reply other threads:[~2005-03-17 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:30 Kris Warkentin [this message]
2005-03-17 22:33 ` Daniel Jacobowitz
2005-03-18 14:47 ` Kris Warkentin
2005-03-18 14:53 ` Daniel Jacobowitz
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=4239F328.5000505@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).