DragonFly bugs List (threaded) for 2005-12
Re: Buildworld error/panic
Sorry I just came across this thread right now, but what you have
suggested is a brilliant idea! It's similar to the way GCC and how some
other applications behave during aborts/panics.
I think this would be something nice to work at, and we can have a
page on the Wiki that explains how to generate core dumps, detailed
and brief back traces (including kernel module trace data etc); and
various other bits and pieces of information on how it should
be done so we don't need to keep repeating it on the lists all the
One of the other key information to provide during panic-time would
be about basic checks that should be done such as, hardware faults
or wrongly compiled kernels etc.
The second thing about searching similar bugs would be nice,
provided that we had a bug database system in active use, but until
that happens we should keep it in mind.
Let me see if I can do something about this after holidays. If it
works well then we can always merge back to the release and stable
hmp at dragonflybsd.org
Jason Smethers wrote:
We need to know what the panic actually was, and a ddb> backtrace
Would it be a good idea to display a URL when the kernel panics? Such a
URL would direct the user to information about how to obtain and report
information about the panic?
Perhaps an extended URL could also be displayed that allows the bug
tracking database to auto search for related panics? Reguardless,
perhaps the bug database could be extended to search for panics that are
already resolved with information inputed from the panic.