Cesar RodriguezandClaude Opus 5.5 7637cac13e fix(libkernel): place guest thread stacks inside the application area ...

On Linux, glibc maps the stack of every guest thread near the top of the
host address space (around 0x7fff00000000). On the console, application
stacks lie inside the application area below 0xFC00000000, and guest code
relies on that: ChakraCore's garbage collector indexes a 4 MiB table with
address >> 18, so it only covers addresses below 1 TiB and reports
Js::OutOfMemoryException for a stack above it.

Map each guest thread's stack with DoMapAnon, which allocates from the
guest arena, behind a PROT_NONE guard page, and pass it to pthread_attr_setstack.
The stack is freed after a join; the stack of a detached thread is freed once its
host thread is gone from /proc/self/task.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-13 16:03:36 +02: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): place guest thread stacks inside the application area

2026-10-13 16:03:36 +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

fix(libkernel): run pthread key destructors before thread release

2026-10-11 12:21:40 -04:00

WindowsThreadLocal.hpp

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

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