-
Notifications
You must be signed in to change notification settings - Fork 179
Fix debugger stepping actions in forked process #1921
New issue
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
Conversation
Fix the debugger stepping state when debugging a process that has been forked from the main process. The new sys.monitoring mechanism didn't fully clear the thread local storage after a fork leading to a state where the forked child process tracked the wrong thread information and was never updated on the latest continue action.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Not sure why that test failed, I'm assuming it's just a bit flaky. I've pushed a commit that adds a test for this scenario as well. |
|
I'll push one more commit to hopefully reduce the diff, looks like Cython's auto generated .c files have trailing spaces so I'll temporarily stop my editor from removing them to avoid troubles in the future. |
|
PR also opened to fix upstream fabioz/PyDev.Debugger#310. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thanks for the fix @jborean93 |
Fix the debugger stepping state when debugging a process that has been forked from the main process. The new sys.monitoring mechanism didn't fully clear the thread local storage after a fork leading to a state where the forked child process tracked the wrong thread information and was never updated on the latest continue action.
Fixes: #1876
I'm not sure what the common practice is for updating the Cython/c files. The diff is pretty large but that's mostly due to line and auto formatting changes that my Cython seems to do. Happy to take them out and let you update those files if you prefer.