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 ...

Andrew Gallatin gallatin at
Wed Aug 3 16:44:36 GMT 2005

Robert Watson [rwatson at] 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 at>
> >  Concept code from:      Neal Fachan <neal at>
> 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?


More information about the cvs-src mailing list