-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
FreeBSD test segfaults masquerading as unhandled task errors #41943
Closed
ararslan opened this issue
Aug 20, 2021
· 1 comment
· Fixed by JuliaPackaging/Yggdrasil#3856 or #42970
Closed
FreeBSD test segfaults masquerading as unhandled task errors #41943
ararslan opened this issue
Aug 20, 2021
· 1 comment
· Fixed by JuliaPackaging/Yggdrasil#3856 or #42970
Labels
Comments
ararslan
added
bug
Indicates an unexpected problem or unintended behavior
system:freebsd
Affects only FreeBSD
labels
Aug 20, 2021
This comment has been minimized.
This comment has been minimized.
This was referenced Oct 24, 2021
This was referenced Nov 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The FreeBSD buildbots have been encountering
UNHANDLED TASK ERROR: EOFError: read end of file
while running the test suite on FreeBSD 12, which I can reproduce locally. What's actually happening is a segfault, but you wouldn't know unless you check/var/log/messages
and/or see the coredump file left behind.Running the tests with a debug build and examining the backtrace of the coredump with GDB, I get:
@vchuravy looked at this a bit and posited that it was a crash in the unwinder while reading process data, caused by a bug in libunwind and/or buggy DWARF emission, and that something may be wrong with asynchronous unwind tables. He recommended the following:
-fno-asynchronous-unwind-tables
. I tried that but the crash persisted.He also noted the following upstream bug reports, which may be a useful breadcrumb (for folks who understand these things 😅)
The text was updated successfully, but these errors were encountered: