From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 21 15:02:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12F6516A53F for ; Thu, 21 Aug 2003 15:02:26 -0700 (PDT) Received: from newman.gte.com (newman.gte.com [132.197.8.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19E3643FBD for ; Thu, 21 Aug 2003 15:02:25 -0700 (PDT) (envelope-from ak03@gte.com) Received: from h132-197-179-27.gte.com (kanpc.gte.com [132.197.179.27]) by newman.gte.com (8.9.1/8.9.1) with ESMTP id SAA04587; Thu, 21 Aug 2003 18:02:13 -0400 (EDT) Received: from kanpc.gte.com (ak03@localhost [127.0.0.1]) h7LM2DF3038946; Thu, 21 Aug 2003 18:02:13 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.9/8.12.9/Submit) id h7LM2CSD038945; Thu, 21 Aug 2003 18:02:12 -0400 (EDT) Date: Thu, 21 Aug 2003 18:02:10 -0400 From: Alexander Kabaev To: "Artem 'Zazoobr' Ignatjev" Message-Id: <20030821180210.44072108.ak03@gte.com> In-Reply-To: <1061503060.1030.4.camel@timon.nist> References: <1061503060.1030.4.camel@timon.nist> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.9.4claws3 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: Dumping a core from inside of process X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 22:02:27 -0000 Look for abort() or SIGABRT. On 21 Aug 2003 21:57:41 +0000 "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. > 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 > > _______________________________________________ > 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