From: Juha Aaltonen <turbopultti@gmail.com>
To: gdb-mailing list <gdb@sourceware.org>
Subject: Re: Bug in 7.7.1 or what? (About signals)
Date: Wed, 11 Nov 2015 01:36:00 -0000 [thread overview]
Message-ID: <CAHR0xd6Mxs6Af0J_CV-cDoxd=DZaKKFyTA_HSTsuFCpsPz7fBA@mail.gmail.com> (raw)
In-Reply-To: <CAHR0xd7Bk_W=wmTw7AJcw1P4M4nzg1zeFuGE_WH5F77-O+Tmpw@mail.gmail.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.
prev parent reply other threads:[~2015-11-11 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 16:47 Juha Aaltonen
2015-11-11 1:36 ` Juha Aaltonen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHR0xd6Mxs6Af0J_CV-cDoxd=DZaKKFyTA_HSTsuFCpsPz7fBA@mail.gmail.com' \
--to=turbopultti@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).