7b5ac83a2a
On a PS5 (firmware 13.60) destroying a rwlock returns 0 even while it is held, and leaves 1 in the handle; every later call on that handle returns EINVAL until it is initialized again. A zero handle is initialized on first use by the scePthreadRwlock calls too. Here a held rwlock returned EBUSY, a destroyed handle became null and was silently re-created by the next POSIX call, and the scePthreadRwlock calls threw on a zero handle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ARCHITECTURE.md | ||
| BUILD.md | ||
| CONVENTIONS.md | ||
| HW_ORACLE.md | ||
| PROGRESS.md | ||
| TechnicalDebt.md | ||