Description of problem: No man page. "-h", "--help" are interpreted as process ids. $ man gcore No manual entry for gcore $ gcore -h Illegal process-id: -h. You can't do that without a process to debug. The program is not being run. gcore: failed to create core.-h $ gcore --help Illegal process-id: --help. You can't do that without a process to debug. The program is not being run. gcore: failed to create core.--help Version-Release number of selected component (if applicable): gdb-7.2.90.20110411-34.fc15.x86_64 How reproducible: Always. Steps to Reproduce: 1. See above. Actual results: See above. Expected results: gcore has a man page. gcore accepts "-h" or "--help". Additional info: It might also be helpful if gcore printed the process name: $ gcore 3309 0x00000036a10adcd0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:82 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) Saved corefile core.3309 $ file core.3309 core.3309: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 'sleep 1000'
Just discovered that gcore is a shell script: $ gcore usage: gcore [-o filename] pid
(In reply to comment #1) > Just discovered that gcore is a shell script: > > $ gcore > usage: gcore [-o filename] pid gcore accepts multiple pids: ... # Loop through pids for pid in $* ...
[patch] gdb_gcore man/help/install [+doc] http://sourceware.org/ml/gdb-patches/2011-04/msg00436.html It is now being tracked upstream and it will get into Fedora 16 unless you reopen it for F-15. Thanks.
(In reply to comment #3) > [patch] gdb_gcore man/help/install [+doc] > http://sourceware.org/ml/gdb-patches/2011-04/msg00436.html > > It is now being tracked upstream and it will get into Fedora 16 unless you > reopen it for F-15. Thanks. Thanks, Jan. That looks great. F16 is fine with me. Very good to know that "programs being dumped remain running unaffected ...".
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.