On 15. 03. 19 21:08, Stanislav Fomichev wrote:
On 03/15, Ivan Vecera wrote:
After some experiences I found that urandom_read does not need to be
linked statically. When the 'read' syscall call is moved to separate
non-inlined function then bpf_get_stackid() is able to find
the executable in stack trace and extract its build_id from it.
But why? Do you have some problems with it being linked statically?
Dependency... you don't need to install static glibc to compile the bpf samples.
Shared libc is available everytime.
Ivan
