mirror of https://github.com/aya-rs/aya
integration-test: attach uprobes to self
For unclear reasons, two of the integration tests related to uprobes were resolving a symbol in libc. The integration-test binary can be built statically, in which case it would not load or reference libc. Statically linking the integration tests and running them in a VM without a userland is a convenient mechanism to exercise the tests against different kernel versions. The fact that the statically linked integration-test binary does not load libc is not the only reason these tests failed in such an environment. In fact, the logic to look in the process's memory maps was not running (because no pid was being passed). Separate logic to determine which object file to use when attempting to resolve a symbol for attaching a uprobe changes its behavior based on whether that target is an absolute path. If the target is not an absolute path, the code searches through the LdSoCache. This cache does not always exist in linux systems; when an attach call is made with a relative path target and there is no /etc/ld.so.cache file, the attach call will fail. This commit does not change that behavior, it merely sidesteps it.pull/717/head
parent
dcc6b84a88
commit
79c9489a4f
Loading…
Reference in New Issue