Date: Mon, 11 Dec 2006 19:11:54 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Julian Elischer <julian@elischer.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: kdb_backtrace 'feature'? Message-ID: <20061212001154.GA87602@xor.obsecurity.org> In-Reply-To: <457DE51C.905@elischer.org> References: <457DE51C.905@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 <sys/stack.h> Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFffPKWry0BWjoQKURAtV3AJ92uIehebL/jagF/HvqJVp/g9hWLACg3PXj FiFNNbCyshp9xLdCETEnk0A= =ppti -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061212001154.GA87602>