Date: Sun, 11 Sep 2005 18:22:02 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Peter Jeremy <peterjeremy@optushome.com.au>, Nate Lawson <nate@root.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf kern.post.mk Message-ID: <p0623090cbf4a4e9293ab@[128.113.24.47]> In-Reply-To: <20050911105821.GA91588@server.vk2pj.dyndns.org> References: <20050911002229.51F4916A471@hub.freebsd.org> <432382BC.5080105@root.org> <20050911105821.GA91588@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:58 PM +1000 9/11/05, Peter Jeremy wrote: > >A number of people have mentioned losing the debug kernel when >they do a rebuild. I can't speak for others, but I mentioned losing the debug-symbol information before the point in time where I actually needed it (due to some sytsem panic). I did not mention building a new kernel. I have removed files from /usr/obj/usr/src without building any new kernel, so the problem does not require a rebuild. >The normal reasons for doing a rebuild are either that you have >updated your source or you've changed your config. The "normal" reasons are not universally true. Ie, even if the "normal" reasons apply 85% of the time, there's 15% of the time when they don't apply. And the coredumps lost in that 15% are still likely to be valuable. Valuable and lost. >In the latter case, I would suggest that the only reason to change >the kernel config is if you are planning on installing a new kernel, >so again you don't need the old debug kernel. Except when you built the new kernel, and it panics IMMEDIATELY upon boot, so you revert back to the previous kernel. And that previous kernel is one which "only occasionally" panics. Now, I know that the above comments do not apply 100% of the time, but they apply often enough that I've been burned (multiple times!) where I did not have the debug symbols for a coredump generated from an unexpected system panic. And I know other freebsd users who have burnt by this same issue. So I'd like to see some change done. Maybe not this one, but this one will do nicely until a better one comes along. >In this change intended for -current only or will it remain in >7-RELEASE? I expect it's much too soon to decide that. Let's get 6.0-release finished before we worry about the low-level details of exactly how 7.0-release should be built! :-) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0623090cbf4a4e9293ab>