openbsd-src/regress/lib/libc/stdio_threading/ at jcs · jcs.org/openbsd-src

jcs.org / openbsd-src

jcs's openbsd hax

openbsd

openbsd-src / regress / lib / libc / stdio_threading /

at jcs 8 folders 1 file

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

While almost all the libc locks are taken and released in the same 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.

2 months ago

Missing $OpenBSD$'s.

11 years ago

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

Make sure the correct errno is reported by warn* or err* and not the errno of an intervening cleanup operation like close/unlink/etc.

11 years ago

While almost all the libc locks are taken and released in the same 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.

2 months ago