[C++] Always use setjmp/longjmp for exceptions
authorPedro Alves <palves@redhat.com>
Tue, 17 Nov 2015 15:17:46 +0000 (15:17 +0000)
committerPedro Alves <palves@redhat.com>
Tue, 17 Nov 2015 15:23:15 +0000 (15:23 +0000)
commiteec461d0a8e7ae14c7fe8f0196ab8d0e30285d83
tree5daba190a7a9e2e54b413e69ffefdb18cd7f315d
parent91ee7171d0886731900ab0238ce3795241d877a4
[C++] Always use setjmp/longjmp for exceptions

We currently throw exceptions from signal handlers (e.g., for
Quit/ctrl-c).  But throwing C++ exceptions from signal handlers is
undefined.  (That doesn't restore signal masks, like siglongjmp does,
and, because asynchronous signals can arrive at any instruction, we'd
have to build _everything_ with -fasync-unwind-tables to make it
reliable.)  It happens to work on x86_64 GNU/Linux at least, but it's
likely broken on other ports.

Until we stop throwing from signal handlers, use setjmp/longjmp based
exceptions in C++ mode as well.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

* common/common-exceptions.h (GDB_XCPT_SJMP, GDB_XCPT_TRY)
(GDB_XCPT_RAW_TRY, GDB_XCPT): Define.
Replace __cplusplus checks with GDB_XCPT checks throughout.
* common/common-exceptions.c: Replace __cplusplus checks with
GDB_XCPT checks throughout.
gdb/ChangeLog
gdb/common/common-exceptions.c
gdb/common/common-exceptions.h
This page took 0.024356 seconds and 4 git commands to generate.