aboutsummaryrefslogtreecommitdiff
path: root/libiberty
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2021-06-18 14:26:30 +0100
committerAndrew Burgess <andrew.burgess@embecosm.com>2021-08-11 12:35:14 +0100
commitd03277b79793adec2508d51f8d789cd3761d9b9d (patch)
tree8f8974ee4e43c775da054ebdb09321eaaef2fd8d /libiberty
parent6aa4f97c2b8a3fe3775d90c7485f4ace610fb103 (diff)
downloadgdb-d03277b79793adec2508d51f8d789cd3761d9b9d.zip
gdb-d03277b79793adec2508d51f8d789cd3761d9b9d.tar.gz
gdb-d03277b79793adec2508d51f8d789cd3761d9b9d.tar.bz2
gdb: register SIGBUS, SIGFPE, and SIGABRT handlers
Register handlers for SIGBUS, SIGFPE, and SIGABRT. All of these signals are setup as fatal signals that will cause GDB to terminate. However, by passing these signals through the handle_fatal_signal function, a user can arrange to see a backtrace when GDB terminates (see maint set backtrace-on-fatal-signal). In normal use of GDB there should be no user visible changes after this commit. Only if GDB terminates with one of the above signals will GDB change slightly, potentially printing a backtrace before aborting. I've added new tests for SIGFPE, SIGBUS, and SIGABRT.
Diffstat (limited to 'libiberty')
0 files changed, 0 insertions, 0 deletions