diff options
author | Tom de Vries <tdevries@suse.de> | 2025-02-24 16:51:10 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2025-02-24 16:51:10 +0100 |
commit | 7915b1753260fb7c62d55d3f2ab00e1e370a5389 (patch) | |
tree | b81f09690db0fabb3c4e5dce5f523dc741e41008 /gdb/cli/cli-style.c | |
parent | a4f974e939e350cdc34089bd59508296abcb4211 (diff) | |
download | binutils-7915b1753260fb7c62d55d3f2ab00e1e370a5389.zip binutils-7915b1753260fb7c62d55d3f2ab00e1e370a5389.tar.gz binutils-7915b1753260fb7c62d55d3f2ab00e1e370a5389.tar.bz2 |
[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 <eliz@gnu.org>
PR gdb/32714
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32714
Diffstat (limited to 'gdb/cli/cli-style.c')
0 files changed, 0 insertions, 0 deletions