From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patchv2] Record objfile->original_name as an absolute path
Date: Mon, 02 Dec 2013 21:26:00 -0000 [thread overview]
Message-ID: <20131202212602.GA19959@host2.jankratochvil.net> (raw)
In-Reply-To: <20131009144629.GC27355@host2.jankratochvil.net>
On Wed, 09 Oct 2013 16:46:29 +0200, Jan Kratochvil wrote:
> gdb/
> 2013-09-25 Doug Evans <dje@google.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * objfiles.c (allocate_objfile): Save original_name as an absolute
> path.
> * objfiles.h (struct objfile): Expand comment on original_name.
> * source.c (openp): Call gdb_abspath.
> * utils.c (gdb_abspath): New function.
> * utils.h (gdb_abspath): Declare.
>
> gdb/testsuite/
> 2013-09-25 Doug Evans <dje@google.com>
>
> * gdb.dwarf/dwp-symlink.c: Fake out gdb to not load debug info
> at start.
> * gdb.dwarf/dwp-symlink.exp: Test trying to load dwp when the binary
> has been specified with a relative path and we have chdir'd before
> accessing the debug info.
Checked in: 04affae3ef7aa124b6ac0ce4f3a54063b7b4784f
Jan
prev parent reply other threads:[~2013-12-02 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 1:29 [RFC] " 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
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 ` Jan Kratochvil [this message]
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=20131202212602.GA19959@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.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