This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Signal values
- From: Daniel Jacobowitz <drow at false dot org>
- To: Fabian Cenedese <Cenedese at indel dot ch>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 2 Sep 2004 11:42:00 -0400
- Subject: Re: Signal values
- References: <5.2.0.9.1.20040902164649.01d53180@NT_SERVER>
On Thu, Sep 02, 2004 at 05:22:22PM +0200, Fabian Cenedese wrote:
> Hi
>
> Is there a uniform declaration of the signals? It seems that gdb is not using
> the same as Linux.
>
> Linux\include\asm-ppc\signal.h (included from ppc-stub.c from the kgdb
> project which I used as base for my stub):
Recent versions of the kgdb stub should translate the signal numbers
correctly, I remember helping them fix this.
>
> #define SIGHUP 1
> #define SIGINT 2
> #define SIGQUIT 3
> #define SIGILL 4
> #define SIGTRAP 5
> #define SIGABRT 6
> #define SIGIOT 6
> #define SIGBUS 7
> #define SIGFPE 8
> #define SIGKILL 9
> #define SIGUSR1 10
> #define SIGSEGV 11
> #define SIGUSR2 12
> #define SIGPIPE 13
> #define SIGALRM 14
> #define SIGTERM 15
These are Linux/PowerPC signal numbers.
> But when I send a 10 gdb tells me it's a SIGBUS which would go along this
> list from binutils/include/gdb/signals.h:
>
> enum target_signal
> {
> TARGET_SIGNAL_0 = 0,
These are remote protocol signal numbers. They are target independent.
> And as aside question: which one is the signal that says the target has
> reached a breakpoint?
SIGTRAP.
--
Daniel Jacobowitz