4 people 3fcafeb420 fix(libkernel): keep the thread stack lock alive through static destruction ...

#9272 keeps liveStacks and protectedStackPages alive through static
destruction so that a late mprotect from an atexit handler can still
look up guest thread stacks. The mutex guarding them is still a static
std::mutex. libstdc++'s std::mutex has a trivial destructor, so it keeps
working on Linux, but libc++ destroys the pthread mutex, and a later lock
throws "mutex lock failed: Invalid argument": on macOS the exit probe of
guest_memory_lifetime fails at its mapping protection stage. The lock is
now allocated and never destroyed, like the maps.

The same change is part of #7201 and #8658.

Co-Authored-By: marion909 <103169397+marion909@users.noreply.github.com>
Co-Authored-By: iamthehimansh <67262056+iamthehimansh@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-22 20:19:51 -04:00

..

include

feat(libkernel): keep the default thread stack size in one settable place

2026-10-21 20:24:13 +03:00

Posix

Merge pull request #8502 from xXPBSXx/fix/pthread-barrier-count-limit

2026-10-21 21:02:25 +02:00

src

fix(libkernel): keep the thread stack lock alive through static destruction

2026-10-22 20:19:51 -04:00