On 26/08/2018 12:19, David Chisnall wrote:
The FreeBSD implementation here looks racy. If one thread dlcloses an object
while another thread is exiting, we can end up calling a function at an invalid
memory address. It also looks as if it may be possible to unload one library,
load another
The FreeBSD implementation here looks racy. If one thread dlcloses an object
while another thread is exiting, we can end up calling a function at an invalid
memory address. It also looks as if it may be possible to unload one library,
load another at the same address, and end up executing
Hi,
I've sent the question below to the Ceph-devel list, asking if any
recent changes would be able to cause this.
But then of course this could stem from FreeBSD libs, and of ports
So the question here is if anybody has gotten these "warnings" in other
tools.
--WjW
