On Tue, Feb 12, 2019 at 06:49:54PM +0000, 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.
That won't work. The backends are version specific. That might explain why you see the backend library be opened and then closed. eblopenbackend will do that if the backend init function returns the wrong version. See also the following in NOTES: - the ABI of the backend modules is not guaranteed. Really, no guarantee whatsoever. We are enforcing this in the code. The modules and their users must match. No third-party EBL module are supported or allowed. The only reason there are separate modules is to not have the code for all architectures in all the binaries. > LD_LIBRARY_PATH = > /p/paradyn/development/sasha/local/lib/elfutils/:/p/paradyn/development/sasha/local/lib/:/p/paradyn/packages/libdwarf/lib:. So assuming you configure with --prefix=/p/paradyn/development/sasha/local and ran make install Then the following should both return "Build for elfutils 175 x86_64-pc-linux-gnu" eu-strings /p/paradyn/development/sasha/local/lib/libdw.so | grep ^Build eu-strings /p/paradyn/development/sasha/local/lib/elfutils/libebl_x86_64.so \ | grep ^Build Hope that helps, Mark
