From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1FYgmz-0004ZB-Ad for mharc-grub-devel@gnu.org; Wed, 26 Apr 2006 05:58:29 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FYgmx-0004Yx-Hq for grub-devel@gnu.org; Wed, 26 Apr 2006 05:58:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FYgmu-0004YQ-Qr for grub-devel@gnu.org; Wed, 26 Apr 2006 05:58:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYgmu-0004YE-Cy for grub-devel@gnu.org; Wed, 26 Apr 2006 05:58:24 -0400 Received: from [194.109.24.26] (helo=smtp-vbr6.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FYgpY-0007OG-W9 for grub-devel@gnu.org; Wed, 26 Apr 2006 06:01:09 -0400 Received: from localhost.localdomain (249-174.surfsnel.dsl.internl.net [145.99.174.249]) by smtp-vbr6.xs4all.nl (8.13.6/8.13.6) with ESMTP id k3Q9wMuw084353 for ; Wed, 26 Apr 2006 11:58:23 +0200 (CEST) (envelope-from mgerards@xs4all.nl) Mail-Copies-To: mgerards@xs4all.nl To: The development of GRUB 2 References: <200604261049.23173.okuji@gnu.org> <87psj4ogsw.fsf@xs4all.nl> <200604261122.03442.okuji@enbug.org> From: Marco Gerards Date: Wed, 26 Apr 2006 12:00:04 +0200 In-Reply-To: <200604261122.03442.okuji@enbug.org> (Yoshinori K. Okuji's message of "Wed, 26 Apr 2006 11:22:03 +0200") Message-ID: <87irowodwb.fsf@xs4all.nl> User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: grub_machine_set_prefix, --enable-mm-debug X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 09:58:27 -0000 "Yoshinori K. Okuji" writes: > On Wednesday 26 April 2006 10:57, Marco Gerards wrote: >> "Yoshinori K. Okuji" 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