Date: Wed, 3 Aug 2005 12:44:27 -0400 From: Andrew Gallatin <gallatin@cs.duke.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha db_trace.c src/sys/arm/arm db_trace.c src/sys/conf files src/sys/i386/i386 db_trace.c src/sys/ia64/ia64 db_trace.c src/sys/kern subr_stack.c src/sys/powerpc/powerpc db_trace.c src/sys/sparc64/sparc64 ... Message-ID: <20050803124427.A65214@grasshopper.cs.duke.edu> In-Reply-To: <20050803123129.W16482@fledge.watson.org>; from rwatson@FreeBSD.org on Wed, Aug 03, 2005 at 12:33:00PM %2B0100 References: <200508030427.j734ReCC049031@repoman.freebsd.org> <20050803123129.W16482@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson [rwatson@FreeBSD.org] wrote: > > On Wed, 3 Aug 2005, Jeff Roberson wrote: > > > Added files: > > sys/kern subr_stack.c > > sys/sys stack.h > > Log: > > - Add support for saving stack traces and displaying them via printf(9) > > and KTR. > > > > Contributed by: Antoine Brodin <antoine.brodin@laposte.net> > > Concept code from: Neal Fachan <neal@isilon.com> > > This sounds really great. I have a local /usr/src/sys/kern/kern_utrace.c > for back-tracing user application stacks that I find quite useful -- I > wonder if we could extend this to also work with user thread stacks? It > can be quite handy for determining how an application reached a > particularly obscure kernel state. It doesn't do the ELF magic, but does > reach into VM to determine what object+offset backs each page pointed to > by a return address. How close is your kern_utrace.c to something that could be used to make a (MacOSX like) crashreporterd deamon which saves application stack traces when an application crashes? Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050803124427.A65214>