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
Occasional segfaults deep in glibc when execing? #2392
Comments
More info. We're blowing up here in exec_job here:
Something terrible is happening that causes show_stackframe() to segfault, in fprintf, but something must have already gone wrong before that. As a wild guess, if write_loop fails due to EPIPE, bad things will happen. Also, shouldn't show_stackframe use write_loop instead of fwprintf? |
I bet I'm right. The open file descriptors were:
(and some more, stripped for brevity) |
What is suspicious about those open file descriptors? That looks OK to me, except for |
I assume it means that the pty master (terminal) is gone. |
See #2393 for a possible fix |
I'm submitting Fedora updates-testing builds with these patch, and I'll ask the original reporter to test. |
Assigning to me to remind myself to review this |
FWIW, this is now in Fedora's updates-testing, so it should get some test coverage over the next few days. |
Fixed by merging #2393. |
I'm seeing various abrt reports that generally look like Fedora bug 1263052, which is the first one I've gotten since updating Fedora's package to fish 2.2.0.
My current best guess is that the iothread_drain_all hack isn't working right.
The text was updated successfully, but these errors were encountered: