public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/23764] Python Objfile.filename documentation does not match behavior (symlinks)
Date: Wed, 06 Apr 2022 17:01:07 +0000 [thread overview]
Message-ID: <bug-23764-4717-Yps88umh1d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23764-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23764
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-04-06
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I think what happened here is that bug #15415 changed gdb to
only partly resolve the objfile's names. And in bug #24143,
I'm considering extending this a bit more.
We could make '.filename' do the resolution itself.
But it may be better to just leave it and update the docs,
on the theory that access to gdb's idea of what is going on
may be valuable, and Python code can easily call realpath on its own.
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2022-04-06 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23764-4717@http.sourceware.org/bugzilla/>
2022-04-06 17:01 ` tromey at sourceware dot org [this message]
2024-05-27 22:31 ` gordon.messmer at gmail dot com
2024-05-27 22:35 ` gordon.messmer at gmail dot com
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=bug-23764-4717-Yps88umh1d@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).