| Issue |
56422
|
| Summary |
Coverage reports wrong accesses with (lotsa) shared libraries
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
nolange
|
I am trying to test a significant number of plugins - shared libraries that are loaded with `dlopen` and `dlsym`.
So for a couple of them have a testsuite, and I went ahead and produced one executable that will dynamically load a plugin, run the tests and then unload the plugin.
Some odd stuff already seems to be happening with the statically linked profiling runtime, see #55682, preventing the runtime to be linked with exporting `__llvm_profile_runtime` just doesn't work for me.
The result is that the coverage seems fine for the plugins having a testsuite (comparing it to a stand-alonge test binary only for that plugin), but a whole bunch of plugins **that aren't even loaded into the process** have hits displayed (i automatically add all plugins to llvm-cov` as `-object`).
I am unsure why this happens, but it seems the "signature" is only compromised of some counts of added instrumentation, not something less likely to cause conflicts like a hash of the binary (build-id).
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
