public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5823] New: extend fdebuginfo to print why debuginfo is rejected
Date: Mon, 03 Mar 2008 20:00:00 -0000	[thread overview]
Message-ID: <20080303200000.5823.cagney@redhat.com> (raw)

frysk uses elfutils to find/verify debuginfo.  Sometimes elfutils chooses to
reject an installed .debug file.  When this occures fdebuginfo should list why
the file is rejected just like it lists files that are accepted.  For instance:

  $ fdebuginfo $$
  /bin/bash --- bad crc check (/usr/lib/debug/usr/bin/ls.debug)
  /usr/lib/libc.so --- no such file or directory
(/usr/lib/debug/usr/lib/libc.so.debug)

this would make it easier for users (and us) to understand why the debug-info we
thought we had installed isn't.

-- 
           Summary: extend fdebuginfo to print why debuginfo is rejected
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com
OtherBugsDependingO 5656,5819
             nThis:


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2008-03-03 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 20:00 cagney at redhat dot com [this message]
2008-04-24 19:05 ` [Bug general/5823] " scox at redhat dot com

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=20080303200000.5823.cagney@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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).