From: Tom Tromey <tom@tromey.com>
To: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Exclude debuginfo files from "outside of ELF segments" warning
Date: Thu, 12 Nov 2020 14:45:19 -0700 [thread overview]
Message-ID: <87imaab66o.fsf@tromey.com> (raw)
In-Reply-To: <20201112205327.2733425-2-keiths@redhat.com> (Keith Seitz via Gdb-patches's message of "Thu, 12 Nov 2020 12:53:27 -0800")
>>>>> "Keith" == Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> writes:
Keith> The short of it is, the ELF program headers for debuginfo files are
Keith> not suited to this particular use case. Consequently, the warning
Keith> generated above really is useless and should be ignored.
Keith> + /* Exclude debuginfo files from this warning, too, since those
Keith> + are often not strictly compliant with the standard. See, e.g.,
Keith> + ld/24717 for more discussion. */
Keith> + if (!is_debuginfo_file (abfd)
Keith> + && bfd_section_size (sect) > 0 && j == num_segments
I didn't know about is_debuginfo_file, so I took a quick look, and it
says:
/* Determine if a bfd is a debuginfo file. Unfortunately there
is no defined method for detecting such files, so we have to
use heuristics instead. */
I wonder if gdb should just use its own idea here, though -- like if the
objfile has a backlink, it is a separate debug file.
I'm ok with this patch though.
thanks,
Tom
next prev parent reply other threads:[~2020-11-12 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 20:53 [PATCH 1/2] Add file name to "Loadable section ... outside " Keith Seitz via Gdb-patches
2020-11-12 20:53 ` [PATCH 2/2] Exclude debuginfo files from "outside " Keith Seitz via Gdb-patches
2020-11-12 21:45 ` Tom Tromey [this message]
2020-11-12 22:18 ` Keith Seitz via Gdb-patches
2020-11-13 13:50 ` Tom Tromey
2020-11-13 17:45 ` Keith Seitz via Gdb-patches
2020-11-12 21:42 ` [PATCH 1/2] Add file name to "Loadable section ... outside " Tom Tromey
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=87imaab66o.fsf@tromey.com \
--to=tom@tromey.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