From: Sasha Da Rocha Pinheiro <darochapinhe@wisc.edu>
To: Mark Wielaard <mark@klomp.org>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>,
Ben Woodard <woodard@redhat.com>
Subject: Re: unknown error after dwarf_cfi_addrframe()
Date: Tue, 12 Feb 2019 17:57:00 -0000 [thread overview]
Message-ID: <BN6PR06MB2932A00756530788193B2E5BA6650@BN6PR06MB2932.namprd06.prod.outlook.com> (raw)
In-Reply-To: <20190212080955.GH10699@wildebeest.org>
Not working even after adding the directory to libebl_*.so to LD_LIBRARY_PATH.
default_abi_cfi is still called returning -1.
Sasha
From: Mark Wielaard <mark@klomp.org>
Sent: Tuesday, February 12, 2019 2:09 AM
To: Sasha Da Rocha Pinheiro
Cc: elfutils-devel@sourceware.org; Ben Woodard
Subject: Re: unknown error after dwarf_cfi_addrframe()
On Tue, Feb 12, 2019 at 07:25:28AM +0000, Sasha Da Rocha Pinheiro wrote:
> Oh this is a whole new thing. How have this worked before without those .so? After downloading and compiling elfutils we only copy libdw and libelf.
The backends are only used for architecture specific ELF things.
Most of DWARF can be understood in an architecture independent way.
But CFI does have some arch specific things.
You should really use make install to get a proper installation,
not just copy some files. Otherwise you might indeed miss the
backends, or translations, etc.
Cheers,
Mark
next prev parent reply other threads:[~2019-02-12 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 22:57 Sasha Da Rocha Pinheiro
2019-02-12 1:15 ` Sasha Da Rocha Pinheiro
2019-02-12 6:47 ` Mark Wielaard
[not found] ` <BN6PR06MB293247BE5B8443B3E3EB967BA6650@BN6PR06MB2932.namprd06.prod.outlook.com>
2019-02-12 8:09 ` Mark Wielaard
2019-02-12 17:57 ` Sasha Da Rocha Pinheiro [this message]
2019-02-12 18:39 ` Ben Woodard
2019-02-12 18:43 ` Sasha Da Rocha Pinheiro
2019-02-12 18:41 ` Sasha Da Rocha Pinheiro
[not found] ` <BN6PR06MB29322B835ECA93DFEEA81C2AA6650@BN6PR06MB2932.namprd06.prod.outlook.com>
2019-02-12 19:47 ` Sasha Da Rocha Pinheiro
2019-02-12 20:58 ` Mark Wielaard
2019-02-12 21:39 ` Sasha Da Rocha Pinheiro
2019-02-12 20:42 ` Mark Wielaard
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=BN6PR06MB2932A00756530788193B2E5BA6650@BN6PR06MB2932.namprd06.prod.outlook.com \
--to=darochapinhe@wisc.edu \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
--cc=woodard@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).