-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[threads] Keep the tid after the thread has finished #5615
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
|
Applied this, not sure if it's causal. I get this failure for I also get failures in |
|
@nealef for that assert at |
|
https://pastebin.ca/3875844
@nealef<https://github.com/nealef> for that assert at domain.c:474, can you get a native stack trace for that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#5615 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAS2-tkMuqp8omWHs7b8ARaCDEVnH3W3ks5skpGegaJpZM4PebXj>.
|
|
Seen the exact same thing with @lewurm two weeks ago: #5502 (comment) |
|
@nealef how reproducible is it before and after applying this commit? The |
|
Reproducible in that it happens during the make check but the tests that fail may differ. This time it was finalizer-abort and finalizer-exit which failed with just the:
"Finalizer" tid=0x0x3ff7d16b910 this=0x0x3ff7d1dc278 , thread handle : 0x3ff780010b0, state : not waiting
Error. I will run it several times tomorrow to see what happens.
I haven’t been able to run the test suite for some days due to the 5615 problem.
Neale
|
|
Actually, it appears that the failures are due to timeouts and that the cleanup after the timeout gives the output I am seeing. I will use —trace to see if I can determine where the hang is.
|
|
gdb shows the following thread attempt to Exit: Thread 2 (Thread 0x3ff8567f910 (LWP 51756)): The thread that appears to be doing the suspend handling shows: Thread 1 (Thread 0x3ff8b5fc740 (LWP 51743)): |
No description provided.