"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Wednesday 26 April 2006 10:57, Marco Gerards wrote:
>> "Yoshinori K. Okuji" <[EMAIL PROTECTED]> 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
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
