From: Tom de Vries Date: Mon, 24 Feb 2025 15:51:10 +0000 (+0100) Subject: [gdb/doc] Fix documentation of handle SIGKILL X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7915b1753260fb7c62d55d3f2ab00e1e370a5389;p=thirdparty%2Fbinutils-gdb.git [gdb/doc] Fix documentation of handle SIGKILL Here ( https://sourceware.org/gdb/current/onlinedocs/gdb.html/Signals.html ) I read: ... GDB has the ability to detect any occurrence of a signal in your program. You can tell GDB in advance what to do for each kind of signal. ... However, here ( https://man7.org/linux/man-pages/man2/ptrace.2.html ) I read: ... While being traced, the tracee will stop each time a signal is delivered, even if the signal is being ignored. (An exception is SIGKILL, which has its usual effect.) ... So, it seems to be that for SIGKILL we can't tell GDB in advance what to do. Fix the documentation to reflect this. Approved-By: Eli Zaretskii PR gdb/32714 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32714 --- diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 19abd97838f..29c0118dda2 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -6900,7 +6900,7 @@ fatal so it can carry out the purpose of the interrupt: to kill the program. @value{GDBN} has the ability to detect any occurrence of a signal in your program. You can tell @value{GDBN} in advance what to do for each kind of -signal. +signal, apart from SIGKILL, which has its usual effect regardless. When specifying a signal by number, @value{GDBN} translates the number to the target platform according to the corresponding signal name.