From owner-freebsd-arch@FreeBSD.ORG Fri Jun 10 21:30:09 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 503D016A43A for ; Fri, 10 Jun 2005 21:30:09 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE6B443D1F for ; Fri, 10 Jun 2005 21:30:08 +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 j5ALU7k9069703; Fri, 10 Jun 2005 17:30:07 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.12.10/8.12.10/Submit) with ESMTP id j5ALU6Pb069698; Fri, 10 Jun 2005 17:30:06 -0400 (EDT) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Fri, 10 Jun 2005 17:30:06 -0400 (EDT) From: Jeff Roberson To: Poul-Henning Kamp In-Reply-To: <9261.1118346707@critter.freebsd.dk> Message-ID: <20050610172746.N16943@mail.chesapeake.net> References: <9261.1118346707@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-arch@freebsd.org, Antoine Brodin 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: Fri, 10 Jun 2005 21:30:11 -0000 On Thu, 9 Jun 2005, Poul-Henning Kamp wrote: > In message <20050608221829.75c2de12.antoine.brodin@laposte.net>, Antoine Brodin writes: > >Hi, > > > > > >With Jeff@'s help, I implemented stack saving/tracing functionality. > > Thankyou! Yes, indeed. Good work Antoine. > > >Another question: Since the stack saving/tracing functionality depends > >on ddb, should kern/subr_stack.c be moved to ddb/stack.c and > >sys/stack.h to ddb/stack.h? > > No. > > This code should be compiled in as standard so that any panic prints > a stacktrace on the console, also for non-KDB kernels. You mean use it to print the unresolved addresses without ddb compiled in? It might be useful to breakout the ddb functionality which parses the symbols, and consider always building in the symbols except perhaps in extreme low memory situations. > > A sysctl to enable grepping a backtrace from core-dumping processes > would be wonderful as well. I'm not sure I understand what you mean here? This is designed to save and display kernel stacks while running. > > > -- > 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. > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >