From: Tom Tromey <tom@tromey.com>
To: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCH] gdb/elfread.c: Use bfd filename instead of objfile->original_name
Date: Tue, 30 Aug 2022 12:01:06 -0600 [thread overview]
Message-ID: <87sflda9wd.fsf@tromey.com> (raw)
In-Reply-To: <CAJDtP-Tyj6veVsF_S-C2g=0u88HTt4DVusRqpZVd+h6rQ+zh8Q@mail.gmail.com> (Aaron Merey via Gdb-patches's message of "Fri, 26 Aug 2022 17:24:20 -0400")
>>>>> Aaron Merey via Gdb-patches <gdb-patches@sourceware.org> writes:
> Ping
Thanks, this is ok.
>> > In some cases original_name is prefixed with gdb's working directory
>> > even though the objfile is not located in the working directory.
Offhand this seems bad.
Tom
next prev parent reply other threads:[~2022-08-30 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 20:07 [PATCH] " Aaron Merey via Gdb-patches
2022-07-05 22:43 ` Aaron Merey via Gdb-patches
2022-08-26 21:24 ` [PING][PATCH] " Aaron Merey via Gdb-patches
2022-08-30 18:01 ` Tom Tromey [this message]
2022-08-31 0:45 ` Aaron Merey via Gdb-patches
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=87sflda9wd.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