Date: Sat, 5 Aug 2006 07:35:14 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/net if_vlan.c Message-ID: <20060804213514.GA760@turion.vk2pj.dyndns.org> In-Reply-To: <6B15CBE0-00E0-4F64-A652-4A4B614975C2@xcllnt.net> References: <200608030959.k739x9N6007207@repoman.freebsd.org> <44D22E2F.4070307@errno.com> <20060803180854.GI97316@comp.chem.msu.su> <200608031458.01134.jhb@freebsd.org> <20060804070348.GR97316@comp.chem.msu.su> <6B15CBE0-00E0-4F64-A652-4A4B614975C2@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2006-Aug-04 09:23:52 -0700, Marcel Moolenaar wrote: >So, putting the kdb_backtrace() under KDB is not a matter of said >function not being present without KDB, it's that we don't want >to emit backtraces when debugging is not enabled. Backtraces are >a debugging tool and it makes sense to emit them only when the >kernel is configured for debugging. I'm not sure this follows. Consider the average end-user who has hir system spit out a "something has gone screwy" error. They post the message into one of the FreeBSD lists and are then told that they need to rebuild their kernel with KDB and DDB, reproduce the error, maybe issue a few magic incantations and post the result. Making backtraces either unconditional or run-time conditional (ie a sysctl to enable/disable them) should remove one interation through the mailing lists and improve the quality of support as seen by users. One of the drivers for DTrace was the view that you can't separate debugging and production because the difficult problems only occur in a production environment. Therefore you need to have a production system that has all your debugging tools available but with no debugging overheads until a problem occurs. IMHO, having kdb_backtrace() invoked unconditionally is a step towards this (as is having debug versions of -RELEASE kernels available). --=20 Peter Jeremy --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE072R/opHv/APuIcRAqo1AJ0eTgQfVcWQId262HVpa73omKQTNgCeIqkd KYHvM7I7YcoEaKrfrG6zEuw= =KUna -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060804213514.GA760>