From owner-freebsd-hackers Wed Feb 28 12:18: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CE25937B71B for ; Wed, 28 Feb 2001 12:18:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1SKDhl23051; Wed, 28 Feb 2001 12:13:43 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102280314.TAA43386@akira.lanfear.com> Date: Wed, 28 Feb 2001 12:17:15 -0800 (PST) From: John Baldwin To: Marc W Subject: RE: Generating Core Dump Programmatically Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Feb-01 Marc W wrote: > > > I'm trying to ensure robust shutdown on my machine. Thus, I've > installed signal handlers for a bunch of nasty looking signals. In my > new handler, after all critical state is saved, I then call abort(3), > and all seems to work well. > > EXCEPT -- some signals generate core files when left with the > default behaviour. Is there some straightforward way to do this? Hmm, perhaps make sure you have the default SIGSEGV handler installed after your cleanup and do: *(int *)NULL = 1; or some such? Then again, the core dump you get may not be all that useful... > thanks. > > marc. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message