From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH][RFC] gdb support in GRUB build system
Date: Tue, 5 Aug 2008 23:54:02 +0200 [thread overview]
Message-ID: <20080805215402.GA4756@thorin> (raw)
In-Reply-To: <20080805135021.55c9a2e8@gibibit.com>
On Tue, Aug 05, 2008 at 01:50:21PM -0700, Colin D Bennett wrote:
> On Tue, 5 Aug 2008 22:14:03 +0200
> Robert Millan <rmh@aybabtu.com> wrote:
>
> > On Tue, Aug 05, 2008 at 07:42:29AM -0700, Colin D Bennett wrote:
> > >
> > > We could make it a 'configure' option like '--enable-debug' or
> > > something, but it seems like minimal overhead to generate the .elf
> > > files for gdb in addition to "real" GRUB files.
> >
> > I'd favour the --enable-debug. Even if it's a small overhead, it
> > becomes a big problem when you are out of space and need to start
> > looking around to see what can be shaved off.
>
> In that case, should --enable-debug be the default, or --disable-debug?
I'd prefer to disable debug as default. What do others think?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-05 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 14:42 [PATCH][RFC] gdb support in GRUB build system Colin D Bennett
2008-08-05 15:05 ` Felix Zielcke
2008-08-05 15:11 ` Colin D Bennett
2008-08-05 15:23 ` Felix Zielcke
2008-08-05 20:14 ` Robert Millan
2008-08-05 20:50 ` Colin D Bennett
2008-08-05 21:54 ` Robert Millan [this message]
2008-08-07 0:26 ` Isaac Dupree
2008-08-07 7:37 ` Felix Zielcke
2008-08-07 15:50 ` Colin D Bennett
2008-08-07 16:07 ` Robert Millan
2008-08-07 17:43 ` Colin D Bennett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080805215402.GA4756@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.