This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Bug in 7.7.1 or what? (About signals)
- From: Juha Aaltonen <turbopultti at gmail dot com>
- To: gdb-mailing list <gdb at sourceware dot org>
- Date: Wed, 11 Nov 2015 03:36:33 +0200
- Subject: Re: Bug in 7.7.1 or what? (About signals)
- Authentication-results: sourceware.org; auth=none
- References: <CAHR0xd7Bk_W=wmTw7AJcw1P4M4nzg1zeFuGE_WH5F77-O+Tmpw at mail dot gmail dot com>
Aargh! Stupid me. They, like all numbers should be HEX digits.
On Mon, Nov 9, 2015 at 6:46 PM, Juha Aaltonen <turbopultti@gmail.com> wrote:
> I was wondering if there is a bug with gdb 7.7.1 when I got:
>
> [r $][T][3][1][#][b][8]Packet received: T31
> ...
> Program received signal SIG37, Real-time event 37.
>
> I was expecting SIGUSR2.
>
> And when I sent T10:
>
> [r $][T][1][0][#][b][5]Packet received: T10
> ...
> Can't send signals to this remote system. SIGURG not sent.
> Sending packet: $c#63...[\x00][\x00][\x00][\x00][\x00][
> r +]Ack
>
> I expected SIGBUS and stopping - not SIGURG and an automatic 'c'-command.