From: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
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: Fri, 13 Nov 2020 09:45:38 -0800 [thread overview]
Message-ID: <a5069b09-773b-f69e-02c1-03f2304bd573@redhat.com> (raw)
In-Reply-To: <87blg1bc29.fsf@tromey.com>
On 11/13/20 5:50 AM, Tom Tromey wrote:
>>> 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.
>
> Keith> Yeah, I debated that, too, but ultimately, I thought it best to do what
> Keith> BFD does. Camaraderie? :-)
>
> Makes sense to me. You can check it in.
>
I have pushed both patches. Thank you for taking a look.
Keith
next prev parent reply other threads:[~2020-11-13 17: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
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 [this message]
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=a5069b09-773b-f69e-02c1-03f2304bd573@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=keiths@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox