Deadlock in one process -?

Can a condition when one process / thread is blocked trying to get the same mutex be called a dead end?

mutex_lock (& ​​mutex) - success
...
mutex_lock (& ​​mutex) - blocked, mutexes not released

It seems that the condition of “unauthorized resource” does not apply: there is only one process / thread, so there is no one case of a non-transitional resource to hold and wait: here is only one process, so as not to wait until another process releases the requested resource

+3
source share
2 answers

yes, it is considered or could potentially lead to a deadlock.

the term is not bound by threads or processes, but requires.

, (mutex) , , . , / , , ?

"", , .

+2

, .

, .

  • . ; , . .
  • : , .
  • : , .
  • : , , , , , . , , P = {P1, P2,..., PN}, P1 , P2, P2 , P3, , PN , P1.

...

Circular Wait , .

+1

All Articles