From owner-freebsd-current@FreeBSD.ORG Tue Dec 12 00:19:44 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 2F4A216A403 for ; Tue, 12 Dec 2006 00:19:44 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E99F543FC8 for ; Tue, 12 Dec 2006 00:10:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9C6B11A4D8D; Mon, 11 Dec 2006 16:11:55 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AB3F0515BC; Mon, 11 Dec 2006 19:11:54 -0500 (EST) Date: Mon, 11 Dec 2006 19:11:54 -0500 From: Kris Kennaway To: Julian Elischer Message-ID: <20061212001154.GA87602@xor.obsecurity.org> References: <457DE51C.905@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: <457DE51C.905@elischer.org> User-Agent: Mutt/1.4.2.2i 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:19:44 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 11, 2006 at 03:09:16PM -0800, Julian Elischer wrote: > I often have the following: >=20 >=20 > 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. >=20 > at some later time, you discover 'A' is bad but now you don't know who > was teh bad caller of x() >=20 >=20 > The solution I'm looking for: >=20 > when x() is called it calls kdb_backtrace, but has teh backtrace written= =20 > to a static 16K buffer instead of being put out the normal way. >=20 > when A is found to be wrong, we can see who the last caller of x() was > and how it was called. >=20 >=20 > I am looking at it now.. but if anyone has any thoughts let me know... See Kris --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFffPKWry0BWjoQKURAtV3AJ92uIehebL/jagF/HvqJVp/g9hWLACg3PXj FiFNNbCyshp9xLdCETEnk0A= =ppti -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn--