From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Only compute realpath when basenames_may_differ is set
Date: Fri, 14 Jun 2019 14:31:00 -0000 [thread overview]
Message-ID: <87zhmkme75.fsf@tromey.com> (raw)
In-Reply-To: <20190530170315.9938-1-tromey@adacore.com> (Tom Tromey's message of "Thu, 30 May 2019 11:03:15 -0600")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> A user noted that, when sources are symlinked, gdb annotations will
Tom> print the real path, rather than the name of the symlink.
Tom> It seems to me that it is better to print the name of the file that
Tom> was actually used in the build, unless there is some reason not to.
Tom> This patch implements this, with the caveat that it will not work when
Tom> basenames-may-differ is enabled. The way this mode is currently
Tom> implemented, returning the symbolic (not real) path is not possible.
Tom> While I think it would be good to redo the source file name cache and
Tom> perhaps integrate it with class source_cache, I haven't done so here.
Tom> Regression tested on x86-64 Fedora 29.
Tom> gdb/ChangeLog
Tom> 2019-05-30 Tom Tromey <tromey@adacore.com>
Tom> * source.c (find_and_open_source): Respect basenames_may_differ.
I'm checking this in now.
Tom
next prev parent reply other threads:[~2019-06-14 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 17:03 Tom Tromey
2019-06-14 14:31 ` Tom Tromey [this message]
2019-06-16 22:34 ` Tom de Vries
2019-06-17 17:30 ` Tom Tromey
2019-08-19 19:26 ` Jonah Graham
2019-09-12 17:47 ` Jonah Graham
2019-11-02 17:43 ` Jonah Graham
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=87zhmkme75.fsf@tromey.com \
--to=tromey@adacore.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