aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2025-03-06 15:50:43 +0000
committerAndrew Burgess <aburgess@redhat.com>2025-03-13 15:33:32 +0000
commite8112abd3a1590820462f59af6db7cb1b6928da1 (patch)
tree55b727602e1a3d66285e646f5bdb26ce1507adbb /gdb/python/python.c
parent86ab2c442ff669481df17681a27bb9c7b9a64289 (diff)
downloadbinutils-e8112abd3a1590820462f59af6db7cb1b6928da1.zip
binutils-e8112abd3a1590820462f59af6db7cb1b6928da1.tar.gz
binutils-e8112abd3a1590820462f59af6db7cb1b6928da1.tar.bz2
gcore/doc: fix mistake in the gcore man page
The gcore man page says that the default prefix for a generated core file will be 'gcore', i.e. we'll create files like 'gcore.pid'. In reality the default is 'core'. As far as I can tell, the default has been 'core' for years, and the docs used to say that the default was 'core', but the docs were changed by mistake in commit: commit 129eb0f1f16dc7a49799a024a7bcb109d954a1e7 Date: Fri Jul 27 00:52:23 2018 -0400 Improve gcore manpage and clarify "-o" option So, lets bring the docs back inline with the code. Approved-By: Tom Tromey <tom@tromey.com> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions