© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
By adding "vdso=0" to kernel command line options and rebooting, my system works well and I can get the following backtrace:
[amg1127@
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(gdb) run 5000
Starting program: /bin/sleep 5000
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGINT, Interrupt.
0xb7fa97f2 in 9�t����
(gdb) bt
#0 0xb7fa97f2 in 9�t����
#1 0xb7ebee50 in nanosleep () from /lib/tls/
#2 0x0804a20a in ?? ()
#3 0xbf92c914 in ?? ()
#4 0x00000000 in ?? ()
The #0 position on stack seems really strange...
After installing coreutils-dbgsym package, I get:
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/
(gdb) run 5000
Starting program: /bin/sleep 5000
Program received signal SIGINT, Interrupt.
0xb7f077f2 in 9�t����
(gdb) bt
#0 0xb7f077f2 in 9�t����
#1 0xb7e1ce50 in nanosleep () from /lib/tls/
#2 0x0804a20a in xnanosleep (seconds=5000) at xnanosleep.c:101
#3 0x08048f04 in main (argc=2, argv=Cannot access memory at address 0x4
) at sleep.c:148
#4 0xb7da0040 in __libc_start_main () from /lib/tls/
#5 0x08048b71 in _start ()