-
Notifications
You must be signed in to change notification settings - Fork 45
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
Failure to unwind stack in an after-fork handler #102
Comments
Oof, I see what we've got wrong:
That 6610 on the 2nd to last line is the parent process's pid/tid, not the child process's. Since we're inside of fork at this point, we seem to be finding a structure somewhere that still holds the old pid/tid, rather than the new one that we've got after fork. And then unwinding is failing because we're asking |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After causing a deadlock in an after-fork handler installed with
pthread_atfork
, an attempt to unwind that process withpystack remote --native-all
is giving meThat's happening because
dwfl_getthread_frames
is not finding any frames, and also not settingdwfl_errno
to something non-zero. Interestingly, this doesn't seem to reproduce witheu-stack
, so we might be doing something wrong here that's causing this.#101 fixes the failure mode that we get here, but we should figure out why unwinding is failing, as both
gdb
andeu-stack
succeed.The text was updated successfully, but these errors were encountered: