From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KR7mN-0003Uk-3T for mharc-grub-devel@gnu.org; Thu, 07 Aug 2008 11:51:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KR7mK-0003QA-LJ for grub-devel@gnu.org; Thu, 07 Aug 2008 11:51:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KR7mJ-0003OY-Mk for grub-devel@gnu.org; Thu, 07 Aug 2008 11:51:52 -0400 Received: from [199.232.76.173] (port=51214 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KR7mJ-0003OO-JJ for grub-devel@gnu.org; Thu, 07 Aug 2008 11:51:51 -0400 Received: from gateway15.websitewelcome.com ([69.41.245.9]:40621) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1KR7mJ-0003jZ-2h for grub-devel@gnu.org; Thu, 07 Aug 2008 11:51:51 -0400 Received: (qmail 24272 invoked from network); 7 Aug 2008 15:58:18 -0000 Received: from gator297.hostgator.com (74.53.228.114) by gateway15.websitewelcome.com with SMTP; 7 Aug 2008 15:58:18 -0000 Received: from c-67-185-142-228.hsd1.wa.comcast.net ([67.185.142.228]:48035 helo=localhost) by gator297.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1KR7mE-0003G0-QN for grub-devel@gnu.org; Thu, 07 Aug 2008 10:51:46 -0500 Date: Thu, 7 Aug 2008 08:50:45 -0700 From: Colin D Bennett To: grub-devel@gnu.org Message-ID: <20080807085045.4afa096f@gibibit.com> In-Reply-To: <1218094642.4021.7.camel@fz.local> References: <20080805074229.3e5862c5@gibibit.com> <20080805201403.GD1113@thorin> <20080805135021.55c9a2e8@gibibit.com> <20080805215402.GA4756@thorin> <1218094642.4021.7.camel@fz.local> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator297.hostgator.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gibibit.com X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: [PATCH][RFC] gdb support in GRUB build system X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 15:51:53 -0000 On Thu, 07 Aug 2008 09:37:22 +0200 Felix Zielcke wrote: > Am Dienstag, den 05.08.2008, 23:54 +0200 schrieb Robert Millan: > > On Tue, Aug 05, 2008 at 01:50:21PM -0700, Colin D Bennett wrote: > > > In that case, should --enable-debug be the default, or > > > --disable-debug? > > > > I'd prefer to disable debug as default. What do others think? > > > Have it disabled by default. > I don't think it's useful to have them for everyone i.e. the average > user. I agree that having debug info for the installed GRUB is not helpful, especially for the general end-user. So files installed by the GRUB install process certainly don't need debugging symbols. My concern was only to generate the required symbol information at build time, not to install it for a real GRUB install, or to package these files for distribution in .rpm, .deb, etc. I don't really care if it's the default or not since I can simply choose my configure options as necessary for the task at hand. If I have a debugging situation, then I can rebuild with debug info, since I'd have to re-start the GRUB/QEMU session anyway to begin debugging. (And I don't use the ridiculously slow QEMU for most stuff anyway.) > Having debug symbols in the userland tools could be maybe a bit useful > for example in the case of the grub-probe segfault I experienced on my > mdraid experiments. True, in that case it makes sense to include debug info (if a distro's other packages include it), since a core dump could be used to debug, or if core dumps aren't enabled, then you could simply re-run it with 'gdb grub-probe' to try to recreate the problem. This doesn't require the whole QEMU virtual machine situation that debugging the GRUB boot loader itself requires. Regards, Colin