Subject: Re: DEBUG/DIAGNOSTIC/LOCKDEBUG by default
To: Matthew Mondor <firstname.lastname@example.org>
From: Bill Stouder-Studenmund <email@example.com>
Date: 11/07/2007 10:53:16
Content-Type: text/plain; charset=us-ascii
On Tue, Nov 06, 2007 at 02:29:54PM -0500, Matthew Mondor wrote:
> On Tuesday, 6 Nov 2007 9:18:35
> Adam Hamsik <firstname.lastname@example.org> wrote:
> > IMHO something like boot -c debug/lockdebug... doesn't hurt and=20
> > should be useable for everyone. if you need debug you can turn it
> > on at boot.
> > is it possible to do this or we have to change to much code for
> > this?
> A possible issue might be performance, considering that as a compile
> option macros may be used which generate no code at all when compiled
> without debugging support.
> A boot option might need for empty function stubs, checks against
> NULL function pointer or boolean option variable in
> performance-critical paths, which could no longer heavily use
> assert/diagnostic features unless the functionality could still
> completely be disabled at compile-time.
You're basically describing the reasons Sun came up with dtrace. :-)
Sounds like we should port dtrace and add boot support. :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)
-----END PGP SIGNATURE-----