From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/21541] No error handling for missing backends
Date: Tue, 13 Jun 2017 16:12:00 -0000 [thread overview]
Message-ID: <bug-21541-10460-V5odFEmxEB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21541-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21541
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|eu-readelf --notes fails to |No error handling for
|dump PRSTATUS data? |missing backends
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to myocytebd from comment #2)
> I looked at: libebl/eblopenbackend.c,
> and found openbackend() implementation surprising:
> 1. It doesn't try relative path from the executable.
> 2. It doesn't try the path from --prefix.
> 3. When it failed to load, it doesn't print any message.
Yes, this has come up before and it is at least surprising to users.
Lets keep this bug open to add some error handling to the ebl backend loading
code so the tools can give at least a warning.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-06-12 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 12:43 [Bug backends/21541] New: eu-readelf --notes fails to dump PRSTATUS data? myocytebd at sina dot com
2017-06-02 13:09 ` [Bug backends/21541] " mark at klomp dot org
2017-06-02 13:18 ` myocytebd at sina dot com
2017-06-13 16:12 ` mark at klomp dot org [this message]
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=bug-21541-10460-V5odFEmxEB@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).