While I was developing ebpf_process function it called my attention the number of processes started by other processes. After to debug the event, I decided to also explicit TGID in this eBPF program, helping developers to understand better their own software.
Test Plan
Get binaries according your LIBC from this link and extract them inside a directory, for example: ../artifacts.
You can also get everything for glibc [here](UPLOAD FILE WITH ALL BINARIES TO SIMPLIFY REVIEWERS).
Extract them running:
$ for i in `ls *.zip`; do unzip $i; rm .gitkeep ; rm $i; done
$ for i in `ls *.xz`; do tar -xf $i; rm $i* ; done
Compile branch an run the following tests:
# make clean; make tester
# for i in `seq 0 3`; do ./kernel/legacy_test --netdata-path ../artifacts --process --content --iteration 1 --pid $i --log-path file_pid$i.txt; done
Every test should ends with Success, unless you do not have a specific target (function) available.
Summary
While I was developing
ebpf_process
function it called my attention the number of processes started by other processes. After to debug the event, I decided to also explicit TGID in this eBPF program, helping developers to understand better their own software.Test Plan
Get binaries according your LIBC from this link and extract them inside a directory, for example:
../artifacts
. You can also get everything for glibc [here](UPLOAD FILE WITH ALL BINARIES TO SIMPLIFY REVIEWERS).Extract them running:
Compile branch an run the following tests:
Every test should ends with
Success
, unless you do not have a specific target (function) available.Additional information
This PR was tested on: