From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 11 13:08:36 2005 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 D36B816A4CE for ; Mon, 11 Apr 2005 13:08:36 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4048043D41 for ; Mon, 11 Apr 2005 13:08:36 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id j3BD8Yws080219 for ; Mon, 11 Apr 2005 09:08:35 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)j3BD8XcZ080205 for ; Mon, 11 Apr 2005 09:08:34 -0400 (EDT) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Mon, 11 Apr 2005 09:08:33 -0400 (EDT) From: Jeff Roberson To: hackers@freebsd.org Message-ID: <20050411085956.Y28571@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Mon, 11 Apr 2005 14:35:39 +0000 Subject: JKH Task: Stack saving/tracing functionality. 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: Mon, 11 Apr 2005 13:08:36 -0000 I have proprietary code from a previous employer of mine that implements some really useful debugging features. I'm looking for someone who is interested in cleaning it up, making it architecture indepenent, and getting it running on current. The code basically allows you to save and manipulate stack information. This would be very useful for things like lockmgr, which right now we can't really pass file:line information down to without making #ifdef mess of all of the APIs as options DEBUG_LOCKs does somewhat today. Lockmgr would have a buffer which contained the last N EIPs up the callstack, and this information could be queried and printed using a simple api. Interested parties please email me. We can discuss this and I can provide source. Thanks, Jeff