Date: Wed, 22 Jun 2005 19:16:37 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: mats.lindberg@se.transport.bombardier.com Cc: freebsd-questions@freebsd.org Subject: Re: Generating coredump's from within a signal handler. Message-ID: <20050622161636.GA11708@orion.daedalusnetworks.priv> In-Reply-To: <OF8E633C28.2159E593-ONC1257028.004C4283-C1257028.004CEA64@UK.BOMBARDIER.TRANSPORT.COM> References: <OF8E633C28.2159E593-ONC1257028.004C4283-C1257028.004CEA64@UK.BOMBARDIER.TRANSPORT.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-06-22 16:00, mats.lindberg@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''?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050622161636.GA11708>