-
Notifications
You must be signed in to change notification settings - Fork 23
Stacktrace-based tool issues #8
Comments
Second bullet implemented. Perf faster but not good enough. |
Found out that hash table dumps for StackTrace maps don't work as expected. Tried to force a dump with StackTrace maps, but turns out the bpf_get_first_key on a StackTrace map doesn't return anything even though there's stuff in the map, unlike regular maps. Kernel bug? Ideally the following BCC patch should work if the kernel was giving us what we wanted:
Another fix could be, if all keys could be provided to BPFd in the same invocation, however that would need modification to individual tools. |
Kernel needs key iteration ability in stackmap for above patch to work. Will work on that soon. |
Turns out bpf_get_next_key for stackmap needed implementation in the kernel, I did that and checked in the patch to Next... to figure out why we see "[unknown]" in stacktraces on ARM64. Symbol look ups has my attention! |
TODO: Update INSTALL.md pointing to mandatory kernel patch |
Symbol look ups when walking stack traces is completely broken for "remote" usecases. |
We may be able to close this issue now. Stacktrace-based tools are now working with the latest symbol lookup patches (in addition to your stackmap changes). If there are other issues, I feel that they should be considered as new GitHub issues instead. |
FIXED:
The text was updated successfully, but these errors were encountered: