public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/24488] ebl_openbackend might use wrong library search path
Date: Sat, 11 May 2019 15:49:00 -0000	[thread overview]
Message-ID: <bug-24488-10460-ydRYJ2WV60@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24488-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24488

--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
Created attachment 11770
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11770&action=edit
Factor out loading of ebl backend library and try multiple times with bin/lib
origin paths

I think we just have to try twice. The first time using the $ORIGIN as if it
came from an executable (in bin/) and then using the $ORIGIN as if it came from
an library (in lib[64]/ or lib/<arch>/). So first time using ../$LIB and second
time just with the elfutils EBL_SUBDIR.

The first is what we do now and always work on multilib systems. The second try
works when loading relative to a library whether on a multilib or multiarch
system.

Then we use the same fallback (not using any path) we used already (to take
advantage of any RPATH or LD_LIBRARY_PATH setting).

Could someone try this out on a Debian based system to see if it works as
intended?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-05-11 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24488-10460@http.sourceware.org/bugzilla/>
2019-04-26 14:54 ` [Bug libdw/24488] abidw: wrong results when running with ASAN runtim maennich at google dot com
2019-04-26 22:30 ` [Bug backends/24488] " mark at klomp dot org
2019-04-27 15:49 ` [Bug backends/24488] ebl_openbackend might use wrong library search path mark at klomp dot org
2019-04-28 16:11 ` fche at redhat dot com
2019-04-28 16:27 ` mark at klomp dot org
2019-05-11 15:49 ` mark at klomp dot org [this message]
2019-05-30 10:42 ` maennich at google dot com
2019-05-30 18:52 ` mark at klomp dot org

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-24488-10460-ydRYJ2WV60@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).