Generating coredump's from within a signal handler.

[Giorgos Keramidas]

On 2005-06-22 16:00, mats.lindberg at se.transport.bombardier.com wrote:
> I'm writing a program that when receiving a SIGTERM
> shall generate a coredump of itself and exit.
> This coredump shall be analysed later on using gdb.
> I've tried to raise(SIGABRT) when handling SIGTERM,
> this generates a coredump, but the stack seems messed
> up when examining it with gdb.

The stack *is* ``messed up'' when a program runs within a signal handler
(where ``messed up'' means signal handlers are not called as normal C
functions, but are entered on exit from a system call using special
stack magic).

What do you see in the gdb backtrace that seems ``messed up''?