public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
	Project Archer <archer@sourceware.org>
Subject: Re: find-debuginfo.sh change for gdb index
Date: Mon, 05 Jul 2010 09:36:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.00.1007051223290.8757@localhost> (raw)
In-Reply-To: <m339w1lkuu.fsf@fleche.redhat.com>

On Fri, 2 Jul 2010, Tom Tromey wrote:

> Tom> For a symbol file X, it looks for X.gdb-index.
>
> Roland> It's not clear to me what that means in the separate .debug case.
> Roland> If "symbol file" means the file with the DWARF, then that file is
> Roland> foo.debug so you will be looking for foo.debug.gdb-index.
>
> Right, that is what we do.
>
> Roland> I think it is preferable for the packaging not to add the new symlinks.
> Roland> It doesn't seem like we really need them, since you can look at the
> Roland> .build-id/xx/yyy.debug symlink target name instead.
>
> Sounds good.
>
> In this case I think the most recent patch I sent is the one to use.

So it would be this patch, right?

--- find-debuginfo.sh.orig	2010-06-29 16:19:42.000000000 -0600
+++ find-debuginfo.sh	2010-06-30 14:41:19.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-gdb-index $d" > /dev/null 2>&1
+}
+
  # Make a relative symlink to $1 called $3$2
  shopt -s extglob
  link_relative()
@@ -224,6 +233,8 @@
      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

Is the necessary patch(es) already in rawhide gdb, I dont see anything 
obviously related in gdb changelogs?

One thing this does is that it forces rpm-build to depend on gdb, which 
hardly is the end of the world, just something to note.

 	- Panu -

  reply	other threads:[~2010-07-05  9:36 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
2010-07-02 19:55                 ` Tom Tromey
2010-07-05  9:36                   ` Panu Matilainen [this message]
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=alpine.LFD.2.00.1007051223290.8757@localhost \
    --to=pmatilai@redhat.com \
    --cc=archer@sourceware.org \
    --cc=roland@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).