From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Cc: pmatilai@redhat.com
Subject: find-debuginfo.sh change for gdb index
Date: Tue, 29 Jun 2010 22:32:00 -0000 [thread overview]
Message-ID: <m3vd91tqpl.fsf@fleche.redhat.com> (raw)
Hi Panu. Roland suggested I contact you as the Fedora RPM maintainer.
This patch adds gdb index creation to find-debuginfo.sh, in support of a
feature I'm proposing for Fedora 14:
https://fedoraproject.org/wiki/Features/GdbIndex
I've tested this just by building some RPMs locally.
If you'd prefer, I can open a bug in bugzilla for this.
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.
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.
Tom
--- find-debuginfo.sh.orig 2010-06-29 16:19:42.000000000 -0600
+++ find-debuginfo.sh 2010-06-29 15:52:08.000000000 -0600
@@ -96,6 +96,15 @@
chmod 444 "$1" || exit
}
+# Create a gdb .index file for $1.
+make_gdb_index()
+{
+ local f="$1"
+ local d="${f%/*}"
+ # We don't care if gdb gives an error.
+ gdb --batch-silent -ex "file $f" -ex "maintenance save-gnu-index $d" > /dev/null 2>&1
+}
+
# Make a relative symlink to $1 called $3$2
shopt -s extglob
link_relative()
@@ -224,9 +233,15 @@
chmod u-w "$f"
fi
+ make_gdb_index "$debugfn"
+
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
fi
done || exit
next reply other threads:[~2010-06-29 22:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 22:32 Tom Tromey [this message]
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
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=m3vd91tqpl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=pmatilai@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).