[PATCH 0/5] GDB Synchronous Signal Handling

[Andrew Burgess]

This series is all about how GDB handles fatal, synchronous, signls
generated from within GDB itself, e.g. SIGFPE, SIGSEGV, etc This is
series has nothing to do with signal from or to the inferior.

Patches #1, #2, and #3 all fix existing issues and make sense to merge
even without the later patches in this series.

Patches #4 and #5 add some new functionality to GDB relating to how
fatal signals are handled.

All feedback welcome,
Thanks,
Andrew

---

Andrew Burgess (5):
  gdb: terminate upon receipt of SIGFPE
  gdb: register signal handler after setting up event token
  gdb: rewrite header comment on async_init_signals
  gdb: print backtrace on fatal SIGSEGV
  gdb: register SIGBUS, SIGFPE, and SIGABRT handlers

 gdb/ChangeLog                                 |  42 ++++
 gdb/NEWS                                      |   6 +
 gdb/config.in                                 |   6 +
 gdb/configure                                 |  51 +++++
 gdb/configure.ac                              |  22 ++
 gdb/doc/ChangeLog                             |   4 +
 gdb/doc/gdb.texinfo                           |  12 ++
 gdb/event-top.c                               | 202 +++++++++++++-----
 gdb/testsuite/ChangeLog                       |   9 +
 gdb/testsuite/gdb.base/bt-on-fatal-signal.c   |  22 ++
 gdb/testsuite/gdb.base/bt-on-fatal-signal.exp | 111 ++++++++++
 gdb/ui-file.h                                 |   9 +
 12 files changed, 447 insertions(+), 49 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/bt-on-fatal-signal.c
 create mode 100644 gdb/testsuite/gdb.base/bt-on-fatal-signal.exp

-- 
2.25.4