[BUG] python tracing reports wrong values about calltop HOT 2 CLOSED

There is race condition with BPF function lookup_or_init(). This is a known behaviour. That 's the reason why lookup_or_try_init() has been added.
There are still 2 drawbacks from my point of view:

• lookup_or_try_init() comes with the version 0.12 of the bcc-tools (pakage name for ubuntu is bpfcc-tools). This version is only packaged with the latest distribution (ubuntu 20.04). So users need to install lastest packages with the ppa coming from iovisor/bcc.
• My tests show that even with lookup_or_try_init() I see race condition in calltop python tracing.

i continue to investiguate on this issue since this is a blocker for me.

from calltop.

It was not a race condition. It was a problem with the hash of the function name. Solution was to use bpf_probe_read_str instead of bpf_probe_read

from calltop.