Re: ERROR: No build ID note found in <object file>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 13, 2017 at 10:58:20PM +0200, Mark Wielaard wrote:
> Right. That is not supposed to happen. ET_REL files (except kernel
> modules) should be skipped by the check.
> 
> > 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.
> 
> Right. The first question is should that object file be packaged?

I don't know about "should", but afl-clang-fast doesn't work if it's
not packaged.

> I assume it is shipped so it can be linked directly into a program that
> needs to be instrumented? But if it isn't actually needed in the package
> then you might just not install it/remove it.
> 
> Could you run file afl-llvm-rt-64.o and/or eu-readelf -h
> afl-llvm-rt-64.o on it to see if it really is an ET_REL file.

Sure:

$ eu-readelf -h /usr/lib64/afl/afl-llvm-rt-64.o 
ELF Header:
  Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
  Class:                             ELF64
  Data:                              2's complement, little endian
  Ident Version:                     1 (current)
  OS/ABI:                            UNIX - System V
  ABI Version:                       0
  Type:                              REL (Relocatable file)
  Machine:                           AMD x86-64
  Version:                           1 (current)
  Entry point address:               0
  Start of program headers:          0 (bytes into file)
  Start of section headers:          4792 (bytes into file)
  Flags:                             
  Size of this header:               64 (bytes)
  Size of program header entries:    0 (bytes)
  Number of program headers entries: 0
  Size of section header entries:    64 (bytes)
  Number of section headers entries: 17
  Section header string table index: 16

> > 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?
> 
> As Omair pointed out the check should be skipped for any non-executable
> file. So check

  $ ls -l /usr/lib64/afl/afl-llvm-rt-64.o
  -rwxr-xr-x. 1 root root 5880 Apr 13 18:15 /usr/lib64/afl/afl-llvm-rt-64.o

OK, that's interesting.  I'll see what happens if it's not executable.
Maybe that is the solution.

> If all fails could you sent me the spec file or srpm and I'll try a
> build locally.

The package is:

  https://koji.fedoraproject.org/koji/packageinfo?packageID=19437

Thanks,

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux