create_gcov report "No buildid found in binary"

[ktap]

Hi,

The create_gcov always report cannot found binary buildid, but my kernel
already compiled with buildid.

[root@localhost autofdo]# ./create_gcov --binary=../linux/vmlinux --profile=../linux/perf.data --gcov=1
E0512 10:06:07.650653 14367 elf_reader.cc:789] Malformed .note.gnu.build-id section.
E0512 10:06:07.657847 14367 sample_reader.cc:233] No buildid found in binary
[root@localhost autofdo]#
[root@localhost autofdo]#
[root@localhost autofdo]# readelf -n ../linux/vmlinux|grep build
GNU 0x00000014 NT_GNU_BUILD_ID (unique build ID bitstring)

[dnovillo]

On Sun, May 11, 2014 at 10:22 PM, Jovi Zhangwei notifications@github.comwrote:

Hi,

The create_gcov always report cannot found binary buildid, but my kernel
already compiled with buildid.

[root@localhost autofdo]# ./create_gcov --binary=../linux/vmlinux
--profile=../linux/perf.data --gcov=1
E0512 10:06:07.650653 14367 elf_reader.cc:789] Malformed
.note.gnu.build-id section.
E0512 10:06:07.657847 14367 sample_reader.cc:233] No buildid found in
binary
[root@localhost autofdo]#
[root@localhost autofdo]#
[root@localhost autofdo]# readelf -n ../linux/vmlinux|grep build
GNU 0x00000014 NT_GNU_BUILD_ID (unique build ID bitstring)

You can ignore this error. It's harmless. It's a remnant of a string that's
inserted by Google's build system. Dehao is going to remove this soon.

Diego.

[danielcdh]

You can simply ignore this error message (which I'll remove soon). But you need to make sure the binary that is running in the production machine has the same name as your "--binary" parameter, otherwise the tool cannot find the binary to match profile.

[danielcdh]

This should have been fixed by d6834df