active2volcano
November 5th, 2010, 08:22 AM
Hi every guru:
Everyone know that we can print coredump's stack-called information by gdb's bt(backtrace) command.
For example:
There is a coredump file named "file1".The program's name is "prog1".We can get the stack-called information by these processes:
1. $> gdb prog1 file1
2.gdb> bt
then there are many stack-called information,such as:
#0 func (n=250) at tst.c:6
#1 0x08048524 in main (argc=1, argv=0xbffff674) at tst.c:30
#2 0x400409ed in __libc_start_main () from /lib/libc.so.6
Then I want to get the stack-called information.but the number of this program's coredump file is more than 200.Next time,there may be more.
Can anyone provide a better way to solve this problem?
Everyone know that we can print coredump's stack-called information by gdb's bt(backtrace) command.
For example:
There is a coredump file named "file1".The program's name is "prog1".We can get the stack-called information by these processes:
1. $> gdb prog1 file1
2.gdb> bt
then there are many stack-called information,such as:
#0 func (n=250) at tst.c:6
#1 0x08048524 in main (argc=1, argv=0xbffff674) at tst.c:30
#2 0x400409ed in __libc_start_main () from /lib/libc.so.6
Then I want to get the stack-called information.but the number of this program's coredump file is more than 200.Next time,there may be more.
Can anyone provide a better way to solve this problem?