From owner-freebsd-arch@FreeBSD.ORG Mon Jun 13 08:16:42 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 060F016A41C for ; Mon, 13 Jun 2005 08:16:42 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id A963243D48 for ; Mon, 13 Jun 2005 08:16:41 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id 57BA21EC351 for ; Mon, 13 Jun 2005 10:16:40 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.4/8.13.3) with ESMTP id j5D8GAfF011810; Mon, 13 Jun 2005 10:16:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bakul Shah From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Jun 2005 08:46:29 PDT." <200506111546.j5BFkToq011515@gate.bitblocks.com> Date: Mon, 13 Jun 2005 10:16:10 +0200 Message-ID: <11809.1118650570@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Antoine Brodin , freebsd-arch@freebsd.org Subject: Re: RFC: Stack saving/tracing functionality. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 08:16:42 -0000 In message <200506111546.j5BFkToq011515@gate.bitblocks.com>, Bakul Shah writes: >> ... but it would be neat if it could also save/print userland stacks >> so that we could get tracebacks from abort()'ing userland programs. > >Along these lines; wouldn't it be neat if there was a sysctl >to leave a segfaulted or aborted process around so that you >can attach a debugger to it and find out what went wrong (and >may be even correct it!)? Debugging a live process (even if >fatally injured) yields more clues as you can poke around at >its I/O connections, its caller process etc. A separate >program can be used to create a coredump if you really wish >to preseve the dead body for later autopsy. Ideally a coredump should include anything sockstat and fstat can tell you about the process. /me longs for the MVS dumps level of details... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.