Kernel callstacks not show correct about blazesym HOT 4 CLOSED

I am looking into this issue.

from blazesym.

BTW, it seems not correct to link C program with this -lrt -ldl -lpthread -lm libblazesym.a according to https://github.com/libbpf/blazesym#link-c-programs, such as gcc CMakeFiles/xx.dir/xx.c.o -o xx -lrt -ldl -lpthread -lm ./libblazesym.a libbpf/libbpf.a -lelf -lz, the ld program complains a lot like this:

/home/xx/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.24.2/src/sys/timer.rs:162: undefined reference to `timer_getoverrun'
./libblazesym.a(nix-1d96e29aba325ff2.nix.dba0ec83-cgu.8.rcgu.o): In function `<nix::sys::timer::Timer as core::ops::drop::Drop>::drop':
/home/xx/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.24.2/src/sys/timer.rs:169: undefined reference to `timer_delete'
collect2: error: ld returned 1 exit status

The sequence of the args matters. If I change it to libblazesym.a -lrt -ldl -lpthread -lm, such as gcc CMakeFiles/xx.dir/xx.c.o -o xx ./libblazesym.a -lrt -ldl -lpthread -lm libbpf/libbpf.a -lelf -lz, the ld succeed.

Maybe the doc needs to change the order?

My GCC version is 7.4.0.

from blazesym.

@woodpenker pull #11 should fix your issue. It should work with only kallsyms or a kernel image. Please check if it fixes your problem. Thank you!

from blazesym.

@woodpenker pull #11 should fix your issue. It should work with only kallsyms or a kernel image. Please check if it fixes your problem. Thank you!

👍 It works! I had tested it with the setting src.params.kernel.kallsyms = NULL and src.params.kernel.kallsyms = "/proc/kallsyms";, both work well. Thanks!

from blazesym.