Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Sasha Da Rocha Pinheiro
I built again in another folder, version .0175, and added that to LD_LIBRARY_PATH. And it seems to work fine. Somehow the version we build with Dyninst cmake is not working. Thanks Sasha From: Mark Wielaard Sent: Tuesday, February 12, 2019 2:57 PM To: Sasha Da Rocha Pinheiro Cc: elfutils-deve

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Mark Wielaard
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

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Mark Wielaard
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.

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Sasha Da Rocha Pinheiro
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. Sasha From: Sasha Da Rocha Pinheiro Sent: Tuesday, February 12, 2019 12:49 PM To: Mark Wielaard Cc: elfutils-devel@sourceware.org

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Sasha Da Rocha Pinheiro
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 th

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Sasha Da Rocha Pinheiro
Below I copy gdb execution from eblopenbackend.c trying to dlopen a dsoname "libebl_x86_64.so". After that it will try to open again, which find something, but culminates to closing it with (void) dlclose (h); (gdb) n 328 void *h = dlopen (dsoname, RTLD_LAZY); (gdb) p dsonmae No sym

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Ben Woodard
Does it work at all if you use the standard RH installed version of elfutils? -ben > On Feb 12, 2019, at 9:57 AM, Sasha Da Rocha Pinheiro > wrote: > > Not working even after adding the directory to libebl_*.so to > LD_LIBRARY_PATH. > default_abi_cfi is still called returning -1. > > Sasha

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Sasha Da Rocha Pinheiro
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 Sent: Tuesday, February 12, 2019 2:09 AM To: Sasha Da Rocha Pinheiro Cc: elfutils-devel@sourceware.org; Ben Woodard Subject: Re: unknown error

Re: unknown error after dwarf_cfi_addrframe()

2019-02-12 Thread Mark Wielaard
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