hayodea 2a60fdd9df Qutex: currOwner should use registered sh_ptr to Lockvoker ...

This ensures that the Lockvoker object we access from currOwner
remains valid past the lifetime of the Lockvoker object that
gets copied and invoked by boost::asio

2025-09-29 14:37:16 -04:00

..

user

Async: add sh_ptr<ContinuationChainLink> to Callback<>

2025-09-27 18:30:09 -04:00

asynchronousBridge.h

AsyncBridge: Fix build warning

2025-09-10 11:38:33 -04:00

asynchronousContinuation.h

Qutex: currOwner should use registered sh_ptr to Lockvoker

2025-09-29 14:37:16 -04:00

asynchronousContinuationChainLink.h

Qutex: currOwner should use registered sh_ptr to Lockvoker

2025-09-29 14:37:16 -04:00

asynchronousLoop.h

AsyncLoop: Add copy constr + assignment op

2025-09-16 18:20:08 -04:00

callback.h

Async: add sh_ptr<ContinuationChainLink> to Callback<>

2025-09-27 18:30:09 -04:00

config.h.in

DevMgr: Add DeviceReattacher daemon plumbing

2025-09-28 23:07:39 -04:00

lockerAndInvokerBase.h

Qutex: currOwner should use registered sh_ptr to Lockvoker

2025-09-29 14:37:16 -04:00

lockSet.h

Debug:Qutex: Add deadlock detection based on elapsed time

2025-09-21 15:11:28 -04:00

preprocessor.h

Rename hk=>smo

2025-07-22 06:48:04 -04:00

qutex.h

Qutex: currOwner should use registered sh_ptr to Lockvoker

2025-09-29 14:37:16 -04:00

serializedAsynchronousContinuation.h

Qutex: currOwner should use registered sh_ptr to Lockvoker

2025-09-29 14:37:16 -04:00

spinLock.h

SpinLock: Add acquire/release() and spinPause()

2025-09-18 23:01:49 -04:00