search for: jitdebuglock

...f race. Theory: with two unit tests A and B running back to back... 1. Unit test A allocates and deallocates a `MemMgr` (or whatever other object we are using for a key) at address X 2. Unit test A calls ` notifyFreeingObject` to free the object at K=X but gets stuck (does not lock) the ` JITDebugLock` mutex here<https://github.com/llvm/llvm-project/blob/3d5360a4398bfa6878f94ca9ac55bc568692c765/llvm/lib/ExecutionEngine/GDBRegistrationListener.cpp#L181> for whatever reason 3. Meanwhile unit test B allocates a `MemMgr` (or whatever other object we are using for a key) at newly freed addre...

...k… >> >> >> >> 1. Unit test A allocates and deallocates a `MemMgr` (or whatever >> other object we are using for a key) at address X >> 2. Unit test A calls ` notifyFreeingObject` to free the object at K=X >> but gets stuck (does not lock) the ` JITDebugLock` mutex here >> <https://github.com/llvm/llvm-project/blob/3d5360a4398bfa6878f94ca9ac55bc568692c765/llvm/lib/ExecutionEngine/GDBRegistrationListener.cpp#L181> >> for whatever reason >> 3. Meanwhile unit test B allocates a `MemMgr` (or whatever other >> objec...

...of race. Theory: with two unit tests A and B running back to back… 1. Unit test A allocates and deallocates a `MemMgr` (or whatever other object we are using for a key) at address X 2. Unit test A calls ` notifyFreeingObject` to free the object at K=X but gets stuck (does not lock) the ` JITDebugLock` mutex here<https://github.com/llvm/llvm-project/blob/3d5360a4398bfa6878f94ca9ac55bc568692c765/llvm/lib/ExecutionEngine/GDBRegistrationListener.cpp#L181> for whatever reason 3. Meanwhile unit test B allocates a `MemMgr` (or whatever other object we are using for a key) at newly freed addre...