Alan Maguire

The fix is simple but needs to be pushed; I'm working on getting that done. Hopefully should be sometime over the next few days.

finally got write access; I've pushed a bunch of changes that Knut and I authored that should hopefully resolve various compilation issues; let me know if you run into any...

hi Pascal On 11/10/19 12:14, pfourguet wrote: > > Hi, > i'm using KTF_OVERRIDE macro to override kernel functions and > KTF_SET_RETURN_VALUE macro to set the returned value of the...

thanks for reporting this issue! I _think_ I may see the problem. It looks like you've enabled per-module coverage, and we have code that avoids memory tracking for the ktf_cov_kmem_cache_alloc_handler...

thanks for reporting this! as you can probably tell thus far we've been a bit x86_64-centric, but ARM support is something we'd definitely like to add. i'll try and resolve...

thanks Pascal! Knut pushed an update I made today which will (I hope) solve this specific issue; I tried adding arm[64] support in general but some things may well still...

hi Pascal, latest ktf should resolve the compilation issues with registers - I've tested it in a KVM-emulated ARM64 environment and build works okay. WRT the struct page issues; do...

hi Pascal, I just updated my ARM64 kernel to 4.18 and ran into the issue with "struct page". The latest KTF has a fix for that. With the updated KTF...

> If users are building BCC with external libbpf package, I guess they are expected to install UAPI headers shipped with libbpf. > > ```shell > $ make install_uapi_headers >...

something like the following might be useful; I did this using the python stapsdt example: ``` $ sudo cat /proc/$(pgrep example.py)/maps|grep pythonapp 7f13289ff000-7f1328a00000 r-xp 00000000 00:01 258616 /memfd:libstapsdt:pythonapp (deleted) 7f1328a00000-7f1328bff000...