From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub_machine_set_prefix, --enable-mm-debug
Date: Wed, 26 Apr 2006 12:00:04 +0200 [thread overview]
Message-ID: <87irowodwb.fsf@xs4all.nl> (raw)
In-Reply-To: <200604261122.03442.okuji@enbug.org> (Yoshinori K. Okuji's message of "Wed, 26 Apr 2006 11:22:03 +0200")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> On Wednesday 26 April 2006 10:57, Marco Gerards wrote:
>> "Yoshinori K. Okuji" <okuji@gnu.org> writes:
>> > On Wednesday 26 April 2006 01:22, Hollis Blanchard wrote:
>> >> Is there a reason not to use the runtime debugging infrastructure we
>> >> have? Most of that is "intensive" as well...
>> >
>> > What do you mean by "the runtime debugging infrastructure"? If you mean
>> > grub_dprintf, it is not enough, since you cannot embed file names and
>> > line numbers where the functions are called.
>>
>> IIRC this is being done automatically. Or do I misunderstand
>> something?
>
> Yes. My point is that I want to embed such information into where
> malloc/realloc/memalign/free is called, but not grub_dprintf is called. If
> you use grub_dprintf, you must embed grub_dprintf into so many places
> manually. My way does not require such rewriting.
How about using a macro as a wrapper. So something like:
#define grub_malloc(x) \
{ \
grub_dprintf (...); \
grub_malloc_int (...) \
}
In that case you can use the existing debugging framework we are all
used to.
--
Marco
next prev parent reply other threads:[~2006-04-26 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FYTpn-0003L4-RP@savannah.gnu.org>
2006-04-25 23:22 ` grub_machine_set_prefix, --enable-mm-debug Hollis Blanchard
2006-04-26 8:49 ` Yoshinori K. Okuji
2006-04-26 8:57 ` Marco Gerards
2006-04-26 9:22 ` Yoshinori K. Okuji
2006-04-26 10:00 ` Marco Gerards [this message]
2006-04-26 10:45 ` Yoshinori K. Okuji
2006-04-26 0:10 ` --enable-mm-debug breakage Hollis Blanchard
2006-04-26 2:06 ` Hollis Blanchard
2006-04-26 8:47 ` Yoshinori K. Okuji
2006-04-26 19:31 ` Yoshinori K. Okuji
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=87irowodwb.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.