| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | While almost all the libc locks are taken and released in the same | guenther | 9 days | 1 | -1/+1 |
| | | | | | | | | | | | libc call, flockfile() and ftrylockfile() can be called when single-threaded and then--while 'holding' the lock--the process can create another thread, resulting in a broken state. Have the f{lock,trylock,unlock}file() APIs *always* do real locking so the exposed state is always consistent. ok dlg@ | ||||
| * | Add regression tests for stdio threading. Originally by blambert with | guenther | 2009-11-19 | 1 | -0/+3 |
| some further hacking by me | |||||
