Hide Forgot
Description of problem: gcore should not output much Version-Release number of selected component (if applicable): gdb-7.2.90.20110703-40.fc15.x86_64 How reproducible: Always. Steps to Reproduce: sleep 1h&p=$!;gcore $p Actual results: [1] 26696 0x00007f0dbaee0cd0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:82 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) Saved corefile core.26696 Expected results: [1] 26696 Saved corefile core.26696 Additional info:
This change happened since: show 8235c43a2ff5e1dfa28c1a39757fd941cbc6454c commit 8235c43a2ff5e1dfa28c1a39757fd941cbc6454c Author: Daniel Jacobowitz <dan> Date: Sun Oct 2 23:01:01 2005 +0000 * gdb_gcore.sh: Use a temporary file. Use gdb from $PATH. GDB before did not print anything due to >/dev/null there. I do not find it easy to suppress just the normal_stop() message. One can still get the original behavior by the >/dev/null redirect of gcore. One can use the option `-o' to specific the gcore filename instead of parsing the one printed by GDB. I do not think a fix is needed.