diff options
| author | Bernd Edlinger <bernd.edlinger@hotmail.de> | 2024-05-20 07:12:30 +0200 |
|---|---|---|
| committer | Bernd Edlinger <bernd.edlinger@hotmail.de> | 2024-10-29 16:02:49 +0100 |
| commit | 7ffd4868a7e22dd2f8126822501bfa18479d715c (patch) | |
| tree | 84b4a33d450834b4723f6ab97dcd4c518c32fb7d /gdb/python | |
| parent | 51527eb809f01a14a2e2a8b1ff104c0b2e4823e0 (diff) | |
| download | gdb-7ffd4868a7e22dd2f8126822501bfa18479d715c.zip gdb-7ffd4868a7e22dd2f8126822501bfa18479d715c.tar.gz gdb-7ffd4868a7e22dd2f8126822501bfa18479d715c.tar.bz2 | |
Fix signal unsafe call inside a signal
It can easily happen that the signal handler function
`handle_fatal_signal` uses various signal unsafe functions.
The problematic functions are `_` and `strsignal` which
can be pre-computed after the `setlocale` call is done.
Unfortunately when compiled with --disable-libbacktrace a
different code path is used, that calls the glibc function
`backtrace` which calls `malloc` and `free` and is therefore
also signal unsafe, that is probably unfixable, so there
is no attempt to fix anything in this code path.
Approved-By: Andrew Burgess <aburgess@redhat.com>
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31713#c9
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions