From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23982 invoked by alias); 17 Mar 2005 22:30:50 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23904 invoked from network); 17 Mar 2005 22:30:46 -0000 Received: from unknown (HELO nimbus.ott.qnx.com) (209.226.137.76) by sourceware.org with SMTP; 17 Mar 2005 22:30:46 -0000 Received: from [10.12.1.181] (MOJOJOJO [10.12.1.181]) by nimbus.ott.qnx.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id G9AHFS5A; Thu, 17 Mar 2005 16:14:22 -0500 Message-ID: <4239F328.5000505@qnx.com> Date: Thu, 17 Mar 2005 22:30:00 -0000 From: Kris Warkentin User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: GDB Subject: Possibly dumb signal mapping question Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-03/txt/msg00177.txt.bz2 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