public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/11300] New: Make the "build ID" method of having separate debug info consider more locations
Date: Fri, 19 Feb 2010 16:51:00 -0000	[thread overview]
Message-ID: <20100219165155.11300.andre.poenitz@nokia.com> (raw)

For the "build ID" method of having separate debug info, is
${debug-file-directory}/.build-id/ab/cdef1234.debug is the only location where
the debug info is searched for. Even with the possibility to have several
locations in 
debug-file-directory this is difficult to handle as one needs to know in advance
(a superset of) the set of shared objects that will be loaded.

It would be nice if the build ID method would take the same locations as the
debug-link based variant (which does not scale well to large files due to the
crc computation).

-- 
           Summary: Make the "build ID" method of having separate debug info
                    consider more locations
           Product: gdb
           Version: 7.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: symtab
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: andre dot poenitz at nokia dot com
                CC: gdb-prs at sourceware dot org,jan dot kratochvil at
                    redhat dot com
 GCC build triplet: i486-linux-gnu
  GCC host triplet: i486-linux-gnu
GCC target triplet: i486-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=11300

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


                 reply	other threads:[~2010-02-19 16:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100219165155.11300.andre.poenitz@nokia.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).