3 people 083c98a067 fix(libkernel): leave a once initializer's own cleanup handlers alone when it throws ...

pthread_once and scePthreadOnce removed their reset handler with a pop
that runs whatever handler is on top of the cleanup stack. An
initializer that pushed a handler of its own and then threw left that
handler on top, so the pop ran it with dangling state. Both now record
the stack top before pushing the reset handler; on a throw they restore
the stack to it and reset the control directly, and a normal return
restores it as well.

Reported in review by Hussein Kadhim, who fixed it the same way.

Co-authored-by: Hussein Kadhim <husseinkad.dev@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 07:49:09 +00:00

..

Cancel.hpp

fix(libkernel): leave a once initializer's own cleanup handlers alone when it throws

2026-10-12 07:49:09 +00:00

Cond.hpp

feat(libkernel): impl pthread condition variables + posix thread attribute queries

2026-09-27 11:43:37 +03:00

Mutex.hpp

feat(libkernel): implement posix mutex locking and timed waits

2026-09-27 11:43:37 +03:00

Pthread.hpp

fix(libkernel): inherit process affinity in new guest threads

2026-10-11 12:44:26 +02:00

Rwlock.hpp

feat(libkernel): implement the pthread_rwlock try and timed lock functions

2026-10-04 17:13:36 +02:00

ThreadLifecycle.hpp

feat(libkernel): implement application heap and thread atexit registration

2026-09-27 11:43:33 +03:00

WindowsThreadLocal.hpp

fix(libkernel): keep Unity GC delivery out of MinGW TLS waits

2026-10-10 03:06:40 +03:00