Source-Changes-D archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: src/sys/arch



Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
> On Sun, Jul 03, 2011 at 03:57:25PM +0100, Mindaugas Rasiukevicius wrote:
> > Thanks for enabling this, however you have ignored points raised on
> > tech-kern@.  In such case, at least DEBUG
> 
> DEBUG is not as usefull as DIAGNOSTIC, and is very verbose.
> My main point is to get KASSERT() back again.
> 
> DEBUG and LOCKDEBUG were mentionned, but I don't remmeber a clear
> consensus about thoses
> 
> > and DDB on panic (plus trace
> > command) should be re-enabled as well.
> 
> I also don't think we did reach a consensus about this either.

Well, I object on adding only DIAGNOSTIC, without DEBUG and DDB trace
enabled, as it is counter productive to the idea to gather more info.
LOCKDEBUG would be useful as well, but its very significant effect to
performance can be understood.

Also, it seems that nobody disagreed on enabling DDB trace (as well as
adding DEBUG option).  What makes you think that we did not reach the
consensus?

> With DDB on panic you don't get a core dump, you just see the system
> hang if running X11.
> With trace (assuming you're not running X11), you have the usefull panic
> message scroll away on a standard VGA screen.

Again, "call ddb_vgapost" was proposed.  You can still coredump, either
manually or just by adding another command.  Also, if automatic coredump
fails (to me it is often the case) - then info is left uncollected.

-- 
Mindaugas


Home | Main Index | Thread Index | Old Index