From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: "Alexandra Hájková" <ahajkova@redhat.com>,
"Andrew Burgess" <aburgess@redhat.com>
Subject: Re: [PATCH v3] gdb: defer warnings when loading separate debug files
Date: Wed, 01 Feb 2023 09:36:33 -0700 [thread overview]
Message-ID: <87edr9pcku.fsf@tromey.com> (raw)
In-Reply-To: <87357ptn3v.fsf@redhat.com> (Andrew Burgess via Gdb-patches's message of "Wed, 01 Feb 2023 15:35:32 +0000")
Andrew> + std::string msg
Andrew> + = string_printf (_("\"%s\": separate debug info file has no "
Andrew> + "debug info"), bfd_get_filename (abfd.get ()));
Andrew> + if (separate_debug_file_debug)
Andrew> + gdb_printf (gdb_stdlog, "%s", msg.c_str ());
Andrew> + warnings_vector->emplace_back (std::move (msg));
Sorry I didn't look at this before, but it seems unfortunate that the
filename can't be styled properly here.
Tom
prev parent reply other threads:[~2023-02-01 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 17:13 Alexandra Hájková
2023-01-24 17:21 ` Alexandra Hájková
2023-02-01 15:35 ` Andrew Burgess
2023-02-01 16:36 ` Tom Tromey [this message]
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=87edr9pcku.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=ahajkova@redhat.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).