This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Possibly dumb signal mapping question


On Thu, Mar 17, 2005 at 04:14:16PM -0500, Kris Warkentin wrote:
> 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?

Your stub should be doing this.  The TARGET_SIGNAL_* constants are the
on-the-wire values.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]