From owner-freebsd-current@FreeBSD.ORG Tue Dec 12 00:46:19 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8521D16A492 for ; Tue, 12 Dec 2006 00:46:19 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outG.internet-mail-service.net (outG.internet-mail-service.net [216.240.47.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75B1F43DAA for ; Tue, 12 Dec 2006 00:42:59 +0000 (GMT) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 11 Dec 2006 16:29:21 -0800 Received: from [10.251.18.229] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id kBC0i5Ep091588; Mon, 11 Dec 2006 16:44:06 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <457DFB48.7020704@elischer.org> Date: Mon, 11 Dec 2006 16:43:52 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Kris Kennaway References: <457DE51C.905@elischer.org> <20061212001154.GA87602@xor.obsecurity.org> In-Reply-To: <20061212001154.GA87602@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: kdb_backtrace 'feature'? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2006 00:46:19 -0000 Kris Kennaway wrote: > On Mon, Dec 11, 2006 at 03:09:16PM -0800, Julian Elischer wrote: >> I often have the following: >> >> >> code x() does some bad thing 'A'.. it's a known thing and you can tell >> where it was done from (x()) but x() tell at the time that it is bad. >> >> at some later time, you discover 'A' is bad but now you don't know who >> was teh bad caller of x() >> >> >> The solution I'm looking for: >> >> when x() is called it calls kdb_backtrace, but has teh backtrace written >> to a static 16K buffer instead of being put out the normal way. >> >> when A is found to be wrong, we can see who the last caller of x() was >> and how it was called. >> >> >> I am looking at it now.. but if anyone has any thoughts let me know... > > See interesting... is there any documentation on how to use this and what its limitations are? man -k stack doesn't provide anything.. grrrrr. > > Kris