gcore produces the broken core bt in GDB displays backtrace abnormally.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gdb
gcore, a subcommand in GDB providing the feature of producing a core dump for currently running processes, produces a broken core dump when the target program sleeps.
Step to reproduce:
$ cd /tmp
$ gcc -x c - -o loop
#include <unistd.h>
main(){
$ ./loop &
[1] 3598
$ gcore 3598
0x00007f78bb59e370 in nanosleep () from /lib/libc.so.6
Saved corefile core.3598
$ gdb loop core.3598
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://
Reading symbols from /tmp/loop...(no debugging symbols found)...done.
[New Thread 3598]
Reading symbols from /lib64/
Loaded symbols for /lib64/
Core was generated by `/tmp/loop'.
#0 0x00007f78bb59e370 in ?? ()
(gdb) bt
#0 0x00007f78bb59e370 in ?? ()
#1 0x00007f78bb59e200 in ?? ()
#2 0x0000000000000000 in ?? ()
(gdb)
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gdb 7.1-1ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Sun Jul 25 14:50:14 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
PATH=(custom, user)
LANG=ja_JP.utf8
SHELL=/bin/bash
SourcePackage: gdb
I can confirm this. gdb cores work with redhat & debian sarge, not not on ubuntu lucid or meerkat.