diff options
| author | Kevin Buettner <kevinb@redhat.com> | 2023-02-27 16:11:37 -0700 |
|---|---|---|
| committer | Kevin Buettner <kevinb@redhat.com> | 2023-02-27 16:20:39 -0700 |
| commit | 53f1f3d4aa7019a159d939b7bd2a27a93d630fda (patch) | |
| tree | 5ebbd72f3dc6866bd22b5da6c6cec49ca26fc9c2 /gdb/top.h | |
| parent | b940a061c0d549dbe981463414da87cb84a8a9bb (diff) | |
| download | gdb-53f1f3d4aa7019a159d939b7bd2a27a93d630fda.zip gdb-53f1f3d4aa7019a159d939b7bd2a27a93d630fda.tar.gz gdb-53f1f3d4aa7019a159d939b7bd2a27a93d630fda.tar.bz2 | |
Guile QUIT processing updates
This commit contains QUIT processing updates for GDB's Guile support.
As with the Python updates, we don't want to permit this code to
swallow the exception, gdb_exception_forced_quit, which is associated
with GDB receiving a SIGTERM.
I've adopted the same solution that I used for Python; whereever
a gdb_exception is caught in try/catch code in the Guile extension
language support, a catch for gdb_exception_forced_quit has been
added; this catch block will simply call quit_force(), which will
cause the necessary cleanups to occur followed by GDB exiting.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=26761
Tested-by: Tom de Vries <tdevries@suse.de>
Approved-By: Pedro Alves <pedro@palves.net>
Diffstat (limited to 'gdb/top.h')
| -rw-r--r-- | gdb/top.h | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -235,7 +235,7 @@ extern void read_command_file (FILE *); extern void init_history (void); extern void command_loop (void); extern int quit_confirm (void); -extern void quit_force (int *, int); +extern void quit_force (int *, int) ATTRIBUTE_NORETURN; extern void quit_command (const char *, int); extern void quit_cover (void); extern void execute_command (const char *, int); |