From: Juha Aaltonen <turbopultti@gmail.com>
To: gdb-mailing list <gdb@sourceware.org>
Subject: Signal numbers?
Date: Fri, 06 Nov 2015 14:46:00 -0000 [thread overview]
Message-ID: <CAHR0xd6Ujxx9YPCs77QS=GtceEjQGwUjRygSFAZZZpBqi4vcOQ@mail.gmail.com> (raw)
I was wondering...
How can I find out which signal numbers GDB uses for which signals?
I got my bare metal "kind of gdb server/stub" working, but I wish I
could give some reasonable signal numbers in the stop-messages.
It's not nice if stop due to a breakpoint is reported to user as
"SIGPIPE" by the gdb. ;-)
I thought I sent SIGUSR2 (signal 12) when the debuggee stopped at
breakpoint in the program code (not one of debugger's) and GDB
notified: "Program received signal SIGTSTP, Stopped (user)."
Also signal 7 seems to come out as SIGEMT instead of SIGBUS
(prefetch/data aborts).
next reply other threads:[~2015-11-06 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 14:46 Juha Aaltonen [this message]
2015-11-24 13:12 ` Pedro Alves
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='CAHR0xd6Ujxx9YPCs77QS=GtceEjQGwUjRygSFAZZZpBqi4vcOQ@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).