Date: Thu, 21 Aug 2003 16:20:23 -0700 From: Joshua Oreman <oremanj@get-linux.org> To: Artem 'Zazoobr' Ignatjev <timon@memphis.mephi.ru> Cc: hackers@freebsd.org Subject: Re: Dumping a core from inside of process Message-ID: <20030821232023.GA14865@webserver> In-Reply-To: <1061503968.1030.11.camel@timon.nist> References: <1061503060.1030.4.camel@timon.nist> <20030821180210.44072108.ak03@gte.com> <1061503968.1030.11.camel@timon.nist>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 21, 2003 at 10:12:49PM +0000 or thereabouts, Artem 'Zazoobr' Ignatjev wrote:
> At Thu, 21.08.2003, 22:02, Alexander Kabaev wrote:
> > Look for abort() or SIGABRT.
> Thanks so far for you and Lev.. Is there the way to specify struct
> sigcontext to it? I still wish to have `correct' registers values to be
> written into coredump, those that were when signal happened, and not
> that were when i did abort()ed manually
Not sure if it would work, but try
__asm__ __volatile__ ("pusha");
at the top of the cleanup function and
__asm__ __volatile__ ("popa");
just before you dump core.
-- Josh
> --
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030821232023.GA14865>