This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
backtrace in core on arm-linux
- From: Baurzhan Ismagulov <ibr at radix50 dot net>
- To: gdb at sourceware dot org
- Date: Mon, 5 Mar 2007 19:43:23 +0100
- Subject: backtrace in core on arm-linux
Hello all,
I can't get the backtrace in a core file on arm-linux. To reproduce:
int main(void) {
for (;;) printf("Hello, world!\n");
}
Compile, run under gdb HEAD, press Ctrl-\, bt works:
#0 0x400cb530 in write () from /lib/libc.so.6
#1 0x40080c40 in _IO_new_file_write () from /lib/libc.so.6
#2 0x4007f764 in new_do_write () from /lib/libc.so.6
#3 0x4007f86c in _IO_new_do_write () from /lib/libc.so.6
#4 0x400800f0 in _IO_new_file_overflow () from /lib/libc.so.6
#5 0x400816c4 in __overflow () from /lib/libc.so.6
#6 0x40078048 in puts () from /lib/libc.so.6
#7 0x000084bc in main () at b.c:7
Run from shell, press Ctrl-\, open core, bt shows:
#0 0x400cb530 in write () from /lib/libc.so.6
#1 0x00003704 in ?? ()
#2 0x00003704 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
How can I fix this?
Thanks in advance,
--
Baurzhan Ismagulov
http://www.kz-easy.com/