-devel@sourceware.org; Ben Woodard
Subject: Re: unknown error after dwarf_cfi_addrframe()
On Tue, Feb 12, 2019 at 07:47:06PM +, Sasha Da Rocha Pinheiro wrote:
> I was using elfutils version 0.175, since we download the lastest.
> But after moving back to 0.173, this problem disappeared. So
On Tue, Feb 12, 2019 at 07:47:06PM +, Sasha Da Rocha Pinheiro wrote:
> I was using elfutils version 0.175, since we download the lastest.
> But after moving back to 0.173, this problem disappeared. So, some
> update after 0.173 broke this.
That is surprising. Are you sure you configured, build
On Tue, Feb 12, 2019 at 06:49:54PM +, Sasha Da Rocha Pinheiro wrote:
> Since the openbackend() tries to dlopen twice, and in the second turn
> it succeeds opening one libebl_x86_64.so, I even tried to redirect that
> symbolic link to a newer version of libebl_x86_64-0.165.so, as seen
> below.
@sourceware.org; Ben Woodard
Subject: Re: unknown error after dwarf_cfi_addrframe()
Since the openbackend() tries to dlopen twice, and in the second turn it
succeeds opening one libebl_x86_64.so, I even tried to redirect that symbolic
link to a newer version of libebl_x86_64-0.165.so, as seen below.
(gdb
No, because we need at least 0.173 and the system version is 0.165.
From: Ben Woodard
Sent: Tuesday, February 12, 2019 12:39 PM
To: Sasha Da Rocha Pinheiro
Cc: Mark Wielaard; elfutils-devel@sourceware.org
Subject: Re: unknown error after dwarf_cfi_addrframe()
Does it work at all if you use
paradyn/development/sasha/dyninst/build.dir/elfutils/src/LibElf/libebl/eblopenbackend.c:329
329 if (h == NULL)
(gdb)
From: Sasha Da Rocha Pinheiro
Sent: Tuesday, February 12, 2019 11:57 AM
To: Mark Wielaard
Cc: elfutils-devel@sourceware.org; Ben Woodard
Subject: Re: unknown error after dwarf_cf
ing -1.
>
> Sasha
>
>
>
> From: Mark Wielaard
> 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
error after dwarf_cfi_addrframe()
On Tue, Feb 12, 2019 at 07:25:28AM +, 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 us
On Tue, Feb 12, 2019 at 07:25:28AM +, 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 o
On Tue, Feb 12, 2019 at 01:15:45AM +, Sasha Da Rocha Pinheiro wrote:
> I found that when libdw will try to get the base CFI from the ABI, the
> function ebl_abi_cfi() ends calling default_abi_cfi() which returns -1, when
> should be calling x86_64_abi_cfi().
> In addition, the symbol x86_64_
I found that when libdw will try to get the base CFI from the ABI, the function
ebl_abi_cfi() ends calling default_abi_cfi() which returns -1, when should be
calling x86_64_abi_cfi().
In addition, the symbol x86_64_abi_cfi in the file libdw.so is not present, but
all the respective default_* on
11 matches
Mail list logo
