-
Notifications
You must be signed in to change notification settings - Fork 11
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
Segmentation fault #13
Comments
hrm... so this has only ever been triggered when a unix signal was delivered? |
Yes and it's not that easy to reproduce (needed like 50 tries) with 4 concurrent lzma compressions going on. |
Reproduced and resolved in cachix/cachix#75 (comment) |
@domenkozar interesting... so do you think there's something that can be done in |
I don't think so, my gut feeling says this was a bug in GHC runtime system for handling SIGINT. But maybe @nh2 can chip in, he has been working on that part. |
@domenkozar I'm very suspicious of it. My RTS SIGINT fixes are mostly about IO, but these functions don't do IO: So I would not be surprised if the crash is a use-after-free when accessing pointers; perhaps that free is done from Haskell? @domenkozar Can you build |
Well, ctrl-c is raised in IO monad so it could be that the gist is in another thread. Did any of RTS SIGINT fixes hit GHC 8.4.x? |
Btw, I tried reproducing the repro locally w/ GHC 8.2.2 (but w/o Nix), but failed to reproduce it... didn't segfaulted for me on several iterations. Could you provide me something equivalent of a cabal freeze file of the install-plan as used by Nix, so that I can try to see to try a configuration that's a bit closer to the one on Nix you where observing the segfaults? |
@hvr sure :) Dependencies with segfault: https://gist.github.com/domenkozar/20cdff299fbd160e2c9b872ac21fd20d |
Yes, I can confirm that taking not-segfaulting nixpkgs commit and using GHC 8.2.2 still means no segfault, so that only leaves one of the library bumps fixed it or that it's a false positive. |
Difference in packages seems to be:
|
In my local testing shows it's async bump. |
Reported in cachix/cachix#75 (comment)
I have a core dump with following bt:
Possibly relevant to #4?
The text was updated successfully, but these errors were encountered: