From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Record objfile->original_name as an absolute path
Date: Fri, 27 Sep 2013 19:37:00 -0000 [thread overview]
Message-ID: <87siwqcayo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130926084713.GA11031@host2.jankratochvil.net> (Jan Kratochvil's message of "Thu, 26 Sep 2013 10:47:13 +0200")
Jan> Maybe that gdb_abspath should be rather done by the caller as there is also
Jan> objfile = allocate_objfile (NULL, "<< JIT compiled code >>", 0);
Jan> and calling gdb_abspath ("<< JIT compiled code >>") does not seem great.
I've wanted an objfile flag for a while that would indicate whether the
underlying BFD corresponds to a file or some other thing.
Right now I think you can see lookups of bogusly-named files coming from
the Python auto-loader.
Tom
next prev parent reply other threads:[~2013-09-27 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 1:29 Doug Evans
2013-09-26 1:54 ` Doug Evans
2013-09-26 8:28 ` Jan Kratochvil
2013-09-26 8:47 ` Jan Kratochvil
2013-09-27 19:37 ` Tom Tromey [this message]
2013-10-08 18:23 ` [patch] OBJF_NOT_FILENAME [Re: [RFC] Record objfile->original_name as an absolute path] Jan Kratochvil
2013-10-08 20:18 ` Tom Tromey
2013-10-09 13:23 ` [commit] " Jan Kratochvil
2013-10-09 14:46 ` [patchv2] Record objfile->original_name as an absolute path Jan Kratochvil
2013-10-09 16:37 ` Doug Evans
2013-10-10 4:58 ` Joel Brobecker
2013-10-10 16:31 ` Doug Evans
2013-10-10 16:37 ` Jan Kratochvil
2013-10-10 18:07 ` Tom Tromey
2013-10-10 18:55 ` Doug Evans
2013-12-02 21:26 ` [commit] " Jan Kratochvil
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=87siwqcayo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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