Quick notes on exec discussion with @qianxichen233 @rennergade @yzhang71. We're going to fulfill with details in the future.
cancelstatus -- need to dig into when fixing the exit issue
pthread id is stored here
-- main thread id is stored (like when we create different threads, we store the main thread id to handle signal etc.)
- everything exit correct. Small interface(..?) and return to wasmtime
- call kernel pthread_cancel and then handle situations in wasmtime
Those problems should related to thread (exit) issue we've talked before.
rev_shm lookup table for shm
// fork(): preserved
// exec(): clear
futex -- create futex table save address of futexes
handle different in fork and exec
remove cv/mutex/semaphore tables
one mutex table to ensure behaviors in fork and exec
maybe thread scheduling in
signal staffs -- portable?
Quick notes on exec discussion with @qianxichen233 @rennergade @yzhang71. We're going to fulfill with details in the future.
cancelstatus -- need to dig into when fixing the exit issue
pthread id is stored here
-- main thread id is stored (like when we create different threads, we store the main thread id to handle signal etc.)
Those problems should related to thread (exit) issue we've talked before.
rev_shm lookup table for shm
// fork(): preserved
// exec(): clear
futex -- create futex table save address of futexes
handle different in fork and exec
remove cv/mutex/semaphore tables
one mutex table to ensure behaviors in fork and exec
maybe thread scheduling in
signal staffs -- portable?