From: Robbie Harwood <rharwood@redhat.com>
To: development@efficientek.com
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH 2/2] Make a "gdb" dprintf that tells us load addresses.
Date: Thu, 14 Oct 2021 13:09:21 -0400 [thread overview]
Message-ID: <jlg1r4nzg72.fsf@redhat.com> (raw)
In-Reply-To: <20211012012916.2ebf5e6f@crass-HP-ZBook-15-G2>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Glenn Washburn <development@efficientek.com> writes:
> I don't agree with suppressing file:line for debug output. I have some
> changes in the pipeline which will allow selectively disabling
> conditions when also using "deubg=all". Suppressing file:line makes it
> harder to figure out where the debug output is coming from to find the
> condition to disable it.
Grep for add-symbol-file or /usr/lib/debug etc. will get there.
> I think solution that we both might find agree able is to prepend "\n"
> to your format string. That way "add-symbol-file" will still start on
> a new-line, which seems to be what you're after.
During a boot with this enabled, you don't get just one line - you get
one for each module (plus the initial one for kernel.exec). So if
nothing intersperses, you can do `set confirm off`, then copy/paste the
block.
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-10-14 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 18:48 [PATCH 0/2] Print out load addresses for .text and .data Robbie Harwood
2021-10-11 18:48 ` [PATCH 1/2] Add grub_qdprintf() - grub_dprintf() without the file+line number Robbie Harwood
2021-10-12 6:14 ` Glenn Washburn
2021-10-11 18:48 ` [PATCH 2/2] Make a "gdb" dprintf that tells us load addresses Robbie Harwood
2021-10-12 6:29 ` Glenn Washburn
2021-10-14 17:09 ` Robbie Harwood [this message]
2021-10-15 20:24 ` Glenn Washburn
2021-10-15 20:55 ` Robbie Harwood
2021-10-16 3:25 ` Glenn Washburn
2021-10-19 21:08 ` Robbie Harwood
2021-10-19 21:57 ` Glenn Washburn
2021-10-20 6:45 ` Thomas Schmitt
-- strict thread matches above, loose matches on Subject: below --
2021-10-16 17:48 Michael Schierl
2021-10-18 20:29 ` Glenn Washburn
2021-10-18 21:04 ` Michael Schierl
2021-10-19 7:06 ` 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=jlg1r4nzg72.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=development@efficientek.com \
--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.