From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>, pmatilai@redhat.com
Subject: Re: find-debuginfo.sh change for gdb index
Date: Wed, 30 Jun 2010 22:14:00 -0000 [thread overview]
Message-ID: <20100630221406.254AC4C33E@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of Wednesday, 30 June 2010 15:25:11 -0600 <m3lj9wrz60.fsf@fleche.redhat.com>
> For a symbol file X, it looks for X.gdb-index.
It's not clear to me what that means in the separate .debug case.
If "symbol file" means the file with the DWARF, then that file is
foo.debug so you will be looking for foo.debug.gdb-index.
A good way to deal with the build-id symlink is to canonicalize_file_name
(aka realpath) them and call the symlink target the real file name (for
user display of a useful file name too). If the gdb build-id support is
doing that, then foo.debug.gdb-index should be found.
I think it is preferable for the packaging not to add the new symlinks.
It doesn't seem like we really need them, since you can look at the
.build-id/xx/yyy.debug symlink target name instead.
It just adds a lot more crapola to each rpm.
Thanks,
Roland
next prev parent reply other threads:[~2010-06-30 22:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 22:32 Tom Tromey
2010-06-29 23:21 ` Roland McGrath
2010-06-30 17:35 ` Tom Tromey
2010-06-30 18:14 ` Roland McGrath
2010-06-30 18:23 ` Tom Tromey
2010-06-30 20:42 ` Tom Tromey
2010-06-30 20:44 ` Roland McGrath
2010-06-30 21:25 ` Tom Tromey
2010-06-30 21:58 ` Tom Tromey
2010-06-30 22:00 ` Tom Tromey
2010-06-30 22:14 ` Roland McGrath [this message]
2010-07-02 19:55 ` Tom Tromey
2010-07-05 9:36 ` Panu Matilainen
2010-07-05 9:48 ` Jan Kratochvil
2010-07-05 10:39 ` Panu Matilainen
2010-07-06 18:35 ` Tom Tromey
2010-07-06 19:14 ` Roland McGrath
2010-07-06 19:41 ` Tom Tromey
2010-07-06 20:28 ` Roland McGrath
2010-07-08 15:56 ` Tom Tromey
2010-07-08 20:36 ` Tom Tromey
2010-07-08 22:53 ` Roland McGrath
2010-07-09 5:07 ` Panu Matilainen
2010-07-09 17:48 ` Tom Tromey
2010-07-30 21:36 ` Tom Tromey
2010-07-30 23:07 ` Roland McGrath
2010-07-30 23:09 ` 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=20100630221406.254AC4C33E@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=archer@sourceware.org \
--cc=pmatilai@redhat.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).