Date: Thu, 21 Aug 2003 18:02:10 -0400 From: Alexander Kabaev <ak03@gte.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: <20030821180210.44072108.ak03@gte.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
Look for abort() or SIGABRT. On 21 Aug 2003 21:57:41 +0000 "Artem 'Zazoobr' Ignatjev" <timon@memphis.mephi.ru> 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. > 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) > -- > Artem 'Zazoobr' Ignatjev <timon@memphis.mephi.ru> > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" -- Alexander Kabaev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030821180210.44072108.ak03>