examine core file after abort()

UNIX for Advanced & Expert Users
1

I'm running Red Hat Linux 2.6.7 on a x86_64 box.
I have a core file from a program that called abort(). Does anyone here know how can I get a backtrace? (Re-creating the error with svd running inside gdb has proved impossible).
% gdb svd core.25223
GNU gdb Red Hat Linux (6.0post-0.20040223.19rh)
...
Core was generated by `svd'.
Program terminated with signal 6, Aborted.
...
#0 0x0000003db9b2dc05 in raise () from /lib64/tls/libc.so.6
(gdb) bt
#0 0x0000003db9b2dc05 in raise () from /lib64/tls/libc.so.6
Cannot access memory at address 0x7fbfffe038
(gdb)

2

gdb - yes
bt - yes

I find Linux's handling of threads to be disastrous, especially in the debugger.

3

Tray this ....

pstack core > pstactoutput.txt

I use this on Sun solaris here.

Peter