diff options
| author | Tom Tromey <tromey@adacore.com> | 2024-12-20 13:16:17 -0700 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2025-01-07 06:42:34 -0700 |
| commit | 844afe8d0e5bc95ad48dd46d6adcdc350f598b7d (patch) | |
| tree | 505705075b25a92628c78c1f996603d5aa508d7b /gdb/python/py-param.c | |
| parent | 15f2f44ad7013019e173487a2362acfccc2bbd18 (diff) | |
| download | binutils-844afe8d0e5bc95ad48dd46d6adcdc350f598b7d.zip binutils-844afe8d0e5bc95ad48dd46d6adcdc350f598b7d.tar.gz binutils-844afe8d0e5bc95ad48dd46d6adcdc350f598b7d.tar.bz2 | |
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.
Diffstat (limited to 'gdb/python/py-param.c')
0 files changed, 0 insertions, 0 deletions