]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
projects / thirdparty / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 15f2f44) | patch
Clarify documentation of signal numbers
authorTom Tromey <tromey@adacore.com>
Fri, 20 Dec 2024 20:16:17 +0000 (13:16 -0700)
committerTom Tromey <tromey@adacore.com>
Tue, 7 Jan 2025 13:42:34 +0000 (06:42 -0700)
commit844afe8d0e5bc95ad48dd46d6adcdc350f598b7d
tree505705075b25a92628c78c1f996603d5aa508d7btree
parent15f2f44ad7013019e173487a2362acfccc2bbd18commit | diff
Clarify documentation of signal numbers

A user was confused by the meaning of signal numbers in the gdb CLI.
For instance, when using "signal 3", exactly which signal is
delivered?  Is it always 3, or is it always SIGQUIT?

This patch attempts to clarify the documentation here.
gdb/doc/gdb.texinfo diff | blob | blame | history
A mirror of the official binutils-gdb repository