消息 [163178]
The problem Richard describes isn´t a lost wakeup. PyCOND_SIGNAL _will_ wake up _at least_ one thread. It just isn't guaranteed to be one of those who previously called PyCOND_WAIT(): It could be a latecomer to the game, including the one who called Signal himself. If no such thread comes in to steal it, then one of the waiting threads _will_ wake up.
None of the internal usages of condition variables makes this assumption about the order of wakeup from PyCOND_WAIT(). |
|
| 日期 |
用户 |
动作 |
参数 |
| 2012-06-19 15:06:25 | kristjan.jonsson | 修改 | recipients:
+ kristjan.jonsson, loewis, paul.moore, pitrou, vstinner, python-dev, sbt |
| 2012-06-19 15:06:25 | kristjan.jonsson | 修改 | messageid: <1340118385.29.0.434001096745.issue15038@psf.upfronthosting.co.za> |
| 2012-06-19 15:06:24 | kristjan.jonsson | 链接 | issue15038 messages |
| 2012-06-19 15:06:24 | kristjan.jonsson | 创建 | |
|