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: Tue, 29 Jun 2010 23:21:00 -0000 [thread overview]
Message-ID: <20100629232147.C019548255@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of Tuesday, 29 June 2010 16:32:38 -0600 <m3vd91tqpl.fsf@fleche.redhat.com>
> I don't know what other changes may be needed to ensure that the proper
> gdb is in the buildroots when this script is run. Also, the proper gdb
> is not actually available yet; cleaning up that patch series is my next
> task.
The rpm-build subpackage will need "Requires: gdb >= V-R". Obviously, the
patch can't go in anywhere until that gdb is built in dist-rawhide.
> I think this should probably be local to Fedora, but if you think it
> should go into upstream RPM, I am happy to try that.
It's certainly Fedora-specific and only for Fedora 14.
> + gdb --batch-silent -ex "file $f" -ex "maintenance save-gnu-index $d" > /dev/null 2>&1
I don't quite understand what file this writes to.
Is it implicitly "<symfile name>.index" in the argument directory?
IMHO, the file name should have "gdb" in the name.
This is really not any very generic sort of index for the information.
> if [ -n "$id" ]; then
> make_id_link "$id" "$dn/$(basename $f)"
> make_id_link "$id" "/usr/lib/debug$dn/$bn" .debug
> +
> + if [ -f "${debugfn}.index" ]; then
> + make_id_link "$id" "/usr/lib/debug$dn/$bn" .debug
> + fi
What's this for? It just repeats the work of making and recording the
build-id symlink to the .debug file. Unless you're being quite subtle
somehow I've missed, this doesn't do anything with the index file.
Do you mean something like:
make_id_link "$id" "/usr/lib/debug$dn/$bn" .index
? That gets you a /usr/lib/debug/.build-id/xx/yyy.index symlink
to ../../usr/bin/foobar.index for example.
Thanks,
Roland
next prev parent reply other threads:[~2010-06-29 23:21 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 [this message]
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
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=20100629232147.C019548255@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).