We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exec
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.)
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?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: