Quoting Philip Rowlands <[EMAIL PROTECTED]>:
$ gdb -x <( printf "run\nbt" ) --args ./segv
Program received signal SIGSEGV, Segmentation fault.
0x0804836e in ?? ()
#0 0x0804836e in ?? ()
#1 0xb7fc0020 in __libc_missing_32bit_uids () from /lib/ld-linux.so.2
#2 0x080483c8 in ?? ()
#3 0xbf8bebe8 in ?? ()
#4 0xb7e7e8c8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#5 0xb7e7e8c8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#6 0x080482b1 in ?? ()
(gdb)
It should *at least* display the program counter, no?
I have followed exactly your segv example on my system and here is the output:
$ gdb -x <( printf "run\nbt" ) --args ./segv
GNU gdb 6.4
Copyright 2005 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 "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0x0804836e in ?? ()
#0 0x0804836e in ?? ()
#1 0x40015ca0 in _dl_argv_internal () from /lib/ld-linux.so.2
#2 0xbfffefe4 in ?? ()
#3 0xbfffefb8 in ?? ()
#4 0x40033555 in __libc_start_main () from /lib/libc.so.6
#5 0x40033555 in __libc_start_main () from /lib/libc.so.6
#6 0x080482b1 in ?? ()
This seems to work as it should.
Best regards,
Adam
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
