Date: Thu, 21 Aug 2003 15:05:12 -0700 From: Lev Walkin <vlm@netli.com> To: Artem 'Zazoobr' Ignatjev <timon@memphis.mephi.ru> Cc: freebsd-hackers@freebsd.org Subject: Re: Dumping a core from inside of process Message-ID: <3F454218.4010209@netli.com> In-Reply-To: <1061503060.1030.4.camel@timon.nist> References: <1061503060.1030.4.camel@timon.nist>
next in thread | previous in thread | raw e-mail | index | archive | help
Artem 'Zazoobr' Ignatjev wrote: > Hello, hackers > > I'm writing some program, which dlopens() a lot of shared objects, and > can do nasty things to it's own memory. Some day I decided to trap fatal > memory signals, like SIGILL, SIGBUS and SIGSEGV, and wrote a handler for > these, which swears with bad words into syslog, dlcloses() all that > objects, and quits. What if a handler dlcloses() something which is already in process of dlclosing() at the time the handler fires? > But today I found that it's very useful - to have coredump handy, since > its eases debug a lot. What is the (correct) way to make a coredump of > your own memory (and, it'll be nice to have all that stack frames and > registers written as they were when the signal did occured, not what > they were when we are already in signal handler) man 3 abort -- Lev Walkin vlm@netli.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F454218.4010209>