RFC: Stack saving/tracing functionality.

[Jeff Roberson]

On Thu, 9 Jun 2005, Poul-Henning Kamp wrote:

> In message <20050608221829.75c2de12.antoine.brodin at 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 at 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
>