From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] add a counter in grub_dprintf
Date: Mon, 30 Jun 2008 13:13:34 -0400 [thread overview]
Message-ID: <1214846014.17554.6.camel@dv> (raw)
In-Reply-To: <20080629112241.GA2347@thorin>
On Sun, 2008-06-29 at 13:22 +0200, Robert Millan wrote:
> On Thu, Jun 26, 2008 at 05:20:51PM +0200, Javier Martín wrote:
> > Whoops, sorry, I meant that grub_mkimage would create two core.img
> > images, one per kernel.img version, and then grub_install would copy
> > them as usual. Then grub_setup would embed/set up the normal core.img
> > or the debug version based on a switch. What I propose is basically
> > modifying grub_mkimage to allow choosing the kernel.img file used and
> > then adding some lines to grub_install so that the two versions of
> > core.img are generated (but only the selected is embedded).
>
> Ah; then it sounds fine, I guess.
Sorry for entering this discussion so late. I can tell from my
experience that most debug code is only useful to debug once specific
problem. Once the problem is fixed, the debug code is not needed. If
another problem is found, then some new debug code should be written to
debug that problem.
Generic debug code may be useful to get information from users if only
they can reproduce the problem. But even then, if may be better to add
a few lines to test certain assumptions rather than try to glean useful
pieces of information from a long generic log.
Adding a complicated mechanism for having debug and non-debug images
looks like an overkill to me. It could create more problems than it
would fix.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-30 17:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 13:31 [PATCH] add a counter in grub_dprintf Robert Millan
2008-06-19 18:42 ` Isaac Dupree
2008-06-21 14:19 ` Robert Millan
2008-06-21 14:35 ` Javier Martín
2008-06-21 14:51 ` Bram Diederik
2008-06-22 11:30 ` Isaac Dupree
2008-06-26 14:08 ` Robert Millan
2008-06-26 15:20 ` Javier Martín
2008-06-29 11:22 ` Robert Millan
2008-06-30 17:13 ` Pavel Roskin [this message]
2008-06-30 17:33 ` Vesa Jääskeläinen
2008-07-01 15:59 ` Robert Millan
2008-07-01 15:59 ` Robert Millan
2008-07-01 16:01 ` Pavel Roskin
2008-07-01 17:19 ` Robert Millan
2008-07-02 0:13 ` Pavel Roskin
2008-07-03 18:08 ` Marco Gerards
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=1214846014.17554.6.camel@dv \
--to=proski@gnu.org \
--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.