From: Robbie Harwood <rharwood@redhat.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org, Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH v2 2/2] Make a "gdb" dprintf that tells us load addresses
Date: Mon, 29 Nov 2021 18:11:36 -0500 [thread overview]
Message-ID: <jlgzgpm7e1j.fsf@redhat.com> (raw)
In-Reply-To: <20211125171902.r7ihwloarofnw2yz@tomti.i.net-space.pl>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Daniel Kiper <dkiper@net-space.pl> writes:
> On Wed, Nov 03, 2021 at 02:22:07PM -0400, Robbie Harwood wrote:
>> From: Peter Jones <pjones@redhat.com>
>>
>> Add a grub_dprintf() call during platform init and during module loading
>> that tells us the virtual addresses of the .text and .data sections of
>> grub-core/kernel.exec and any modules it loads.
>>
>> Specifically, it displays them in the gdb "add-symbol-file" syntax, with
>> the presumption that there's a variable $grubdir that reflects the path
>> to any such binaries.
>
> Could you tell us why this thing has to be displayed as a part of debug
> messages? Could you create a separate command which would do the same?
I don't follow what you're suggesting. It's debug output and gdb is a
debugger. What would you have it do instead?
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-11-29 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 18:22 [PATCH v2 0/2] Print out load addresses for .text and .data Robbie Harwood
2021-11-03 18:22 ` [PATCH v2 1/2] Add gdb-friendly output support to grub_real_dprintf() Robbie Harwood
2021-11-03 18:22 ` [PATCH v2 2/2] Make a "gdb" dprintf that tells us load addresses Robbie Harwood
2021-11-25 17:19 ` Daniel Kiper
2021-11-29 23:11 ` Robbie Harwood [this message]
2021-11-30 16:08 ` Daniel Kiper
2021-12-01 16:08 ` Peter Jones
2021-12-01 16:42 ` Daniel Kiper
2022-01-26 8:02 ` Glenn Washburn
2022-01-27 8:19 ` Glenn Washburn
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=jlgzgpm7e1j.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=pjones@redhat.com \
/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.