Is there a way to debug `Mutex` deadlocks caused by recursion?

# coroutines

[Marc Knaup]

Is there a way to debug Mutex deadlocks caused by recursion?

[octylFractal]

there's the owner parameter, you can pass that and it will throw if you re-lock with the same owner

[Marc Knaup]

Yes, but that doesn’t help me with accidental recursion?

[octylFractal]

depends on your choice of owner I guess

[octylFractal]

if you were to store an element in the coroutine context, it would still be there post-recursion, so you could initialize e.g. coroutineContext[MyDebugElement] = coroutineContext[MyDebugElement] ?: Any(), and then pass that as the owner. if you recurse, then you'll use the same unique object and it'll throw

[Marc Knaup]

Hmm, it wouldn’t be inherited by lauched coroutines I presume?

[octylFractal]

no, it wouldn't

[louiscad]

It'd actually, unless it is replaced. That's how it works for all coroutineContext elements, like ContinuationInterceptor (CoroutineDispatcher implements it).

[octylFractal]

oh, well I guess it depends on how you launch

[octylFractal]

if you do it in coroutineScope {} or similar then yes

[octylFractal]

but if you're legitimately switching to a new context via a separate scope, then no