On Wed, Jul 3, 2019 at 7:53 AM Mark Wielaard <m...@klomp.org> wrote: > Thanks for the file, it is indeed pretty big :) > But I am not able to replicate the issue with elfutils from git trunk. > commit 31c8b3f098b0654db8f573b2a15d5b6d07d4d3b0 > > And both the produced chrome_elfutil_test.stripped and > chrome_elfutil_test.debug files seem valid ELF files.
I figured out the problem on my side. The strip binary dynamically linked to /usr/lib/x86_64-linux-gnu/libelf.so.1 and friends. Once I set LD_LIBRARY_PATH, I got the expected output. > But you might not be using the upstream build system, and you might use > different flags to call it. So, two questions. How did you build your > eu-strip binary? And how do you invoke it? I'm building at the same commit on 64-bit Linux: git clone git://sourceware.org/git/elfutils.git cd elfutils autoreconf -i -f ./configure --enable-maintainer-mode make make check cp ./src/strip /path/to/chrome/src/buildtools/third_party/eu-strip/bin/eu-strip Then I did the build on the Chromium side, which essentially runs: strip -o chrome.stripped -f chrome.debug chrome
