From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Add grub_dcprintf for continuations without file/line
Date: Wed, 28 Jul 2010 17:42:36 +0300 [thread overview]
Message-ID: <4C5041DC.1030908@gmail.com> (raw)
In-Reply-To: <20100725030948.GA25314@feather>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On 07/25/2010 06:09 AM, Josh Triplett wrote:
> The attached patch adds a new variant of grub_dprintf, grub_dcprintf,
> which avoids printing the __FILE__:__LINE__: prefix. This allows
> printing a single line with multiple print statements; for instance:
>
> grub_dprintf("some_module", "Thingy: ");
> print_complicated_thingy(thingy);
> grub_dcprintf("some_module", ", more details here\n");
>
> Without the dcprintf variant, this line will contain three different
> file/line prefixes.
>
> I also added support for a "no-file-line" token in the debug environment
> variable, which turns off the file/line prefixes entirely.
>
>
core is very size sensitive. You need a valid usecase to justify such a
feature in it. It feels like useful only for dumping a mass of info. In
practice users can only report back around 4-5 lines, sometimes a
compelete screen by taking its picture, so this info would be lost in
bugreports anyway. If you're developping something you usually need a
dump in that exact place only once and then using grub_printf is usually
easier.
> - Josh Triplett
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2010-07-28 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 3:09 [PATCH] Add grub_dcprintf for continuations without file/line Josh Triplett
2010-07-28 14:42 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4C5041DC.1030908@gmail.com \
--to=phcoder@gmail.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.