On 04/13/2017 11:59 AM, Richard W.M. Jones wrote: > I'm trying to compile native LLVM support into American Fuzzy Lop. > Unfortunately debuginfo generation fails with: > > + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /home/rjones/d/fedora/american-fuzzy-lop/master/afl-2.41b > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-tmin > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-analyze > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-gotcpu > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-showmap > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-clang-fast > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-gcc > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/bin/afl-fuzz > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/lib/afl/afl-llvm-pass.so > extracting debug info from /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/lib/afl/afl-llvm-rt-64.o > *** ERROR: No build ID note found in /home/rjones/rpmbuild/BUILDROOT/american-fuzzy-lop-2.41b-2.fc27.x86_64/usr/lib/afl/afl-llvm-rt-64.o > error: Bad exit status from /var/tmp/rpm-tmp.lnlcV6 (%install) > > Notice that the file that fails is a C object file (not a shared > library), and C object files apparently don't have build IDs. > Was the object file built with clang or gcc? -Tom > I can't work out how to add a build ID. All the workarounds involve > use of the linker (eg. -Wl,-B,...) but that doesn't help as the linker > is never invoked on object files. > > While it's a bit odd that LLVM is using an object file instead of a > shared library, I guess it does that for ... reasons. > > So is there a way to get find-debuginfo.sh to tolerate these files? > (A cursory look at find-debuginfo.sh doesn't show anything obvious, > but I could be missing something). Or maybe there's another way to > solve this? > > Rich. > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
