This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb displaying incorrect signal names with remote target ?
- From: Daniel Jacobowitz <drow at false dot org>
- To: Julian Smith <jsmith at undo-software dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 14 Oct 2009 17:01:12 -0400
- Subject: Re: gdb displaying incorrect signal names with remote target ?
- References: <20091014214827.7259ea9e.jsmith@undo-software.com>
On Wed, Oct 14, 2009 at 09:48:27PM +0100, Julian Smith wrote:
> The inferior is receiving SIGUSR1 (signal number 10 on my i386 Linux
> system), thus the remote target sends a packet `S0a' to gdb.
That's your mistake right there :-)
>From the manual:
The `C', `c', `S', `s', `vCont', `vAttach', `vRun', `vStopped', and `?'
packets can receive any of the below as a reply. Except for `?' and
`vStopped', that reply is only returned when the target halts. In the
below the exact meaning of "signal number" is defined by the header
`include/gdb/signals.h' in the GDB source code.
--
Daniel Jacobowitz
CodeSourcery