Kernel dump out of sync with gdb stack trace

Question

I have a program that crashes due to a segmentation error. The main file is created.

running the kernel in gdb gives me the following:

HP gdb 6.1 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.

The kernel was created by `gcpf1fwcApp '.
The program terminated with signal 6, interrupted.

I used the command

stream applies all bt

When I check the stack trace, I get an error in the main thread, which is pending.

However, when I run the same program in GDB, I get a completely different error in the stack trace. Which seems more correct than the main dump.

The program has 31 threads.

Why am I getting such a difference?

Answer 1

, .

thread apply all where , abort() ing.

GDB , SIGABRT, , , .

(post-mortem) GDB , , , . Linux , - , GDB Linux . , HP-UX , GDB "" .