Re: Implement lbr-as-callgraph v10

[Andi Kleen]

> Segmentation fault (core dumped)
> [root@zoo ~]#
> 
> Rebuilding with DEBUG=1 I get this backtrace:

Ok it crashes inside libbfd while resolving the line. 
Not much I can do about it. 

Could file a bug with the binutils people, if you have a test case?

> 
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `perf report --stdio --no-children --branch-history'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x000000000053ab10 in read_unsigned_leb128 ()
> Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-9.fc20.x86_64 elfutils-libelf-0.160-1.fc20.x86_64 elfutils-libs-0.160-1.fc20.x86_64 libunwind-1.1-3.fc20.x86_64 nss-softokn-freebl-3.17.2-1.fc20.x86_64 numactl-libs-2.0.9-2.fc20.x86_64 slang-2.2.4-11.fc20.x86_64 xz-libs-5.1.2-12alpha.fc20.x86_64
> (gdb) bt
> #0  0x000000000053ab10 in read_unsigned_leb128 ()
> #1  0x00000000005485d7 in find_abstract_instance_name.isra ()
> #2  0x0000000000548756 in find_abstract_instance_name.isra ()
> #3  0x0000000000548756 in find_abstract_instance_name.isra ()
> #4  0x0000000000548d31 in scan_unit_for_symbols ()
> #5  0x00000000005496c9 in comp_unit_find_nearest_line ()
> #6  0x000000000054a6ca in find_line.part ()
> #7  0x00000000005606ca in _bfd_elf_find_nearest_line_discriminator ()
> #8  0x00000000005607db in _bfd_elf_find_nearest_line ()
> #9  0x00000000004dabf1 in find_address_in_section (abfd=0xfd522f0, section=0xe8be528, data=0xfa50c30) at util/srcline.c:100
> #10 0x000000000053cbdc in bfd_map_over_sections ()
> #11 0x00000000004dae84 in addr2line (dso_name=0xe89fe70 "/usr/lib/debug/usr/lib64/firefox/libxul.so.debug", addr=24667432, file=0x7fff3981f9c0, line=0x7fff3981f9bc, dso=0x22a0b50) at util/srcline.c:168
> #12 0x00000000004db017 in get_srcline (dso=0x22a0b50, addr=24667432, sym=0xf6b93f0, show_sym=true) at util/srcline.c:276
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/