-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
nix-instantiate terminated by signal 11, --show-trace has no effect #35
Comments
A segfault in the evaluator is usually due to an infinite recursion in the Nix expression. GDB says:
repeated a few thousand times. |
I've tested a bit, and I think it's not a bug in |
It seems I can "fix" this by changing the definition of the library function |
How do we proceed with this issue? Would it be possible to commit the fix to |
@kosmikus, can you commit your fix? In general Nix expressions shouldn't recurse too deeply because the C stack is not infinite (well, not until we can use GCC's -fsplit-stack). The crashNix expression goes over 80000 levels deep. It would be nice to give a better error message than "signal 11", but there is no portable way to detect a stack overflow. |
I had hesitated committing the fix because these are central library functions which may affect other things, and I haven't checked if my new version returns all results in the same order. But yes, I can try to do it. |
Committed as NixOS/nixpkgs@3fbd694. |
The crashes in |
Update <nixpkgs/nixos> path in documentation.
Add static nix to release.nix
housekeeping: enable devenv, automatic updates, CLA+license
Define the following attribute in
~/.nixpkgs/config.nix
and run:
This may very well be a bug in the
ghtWithPackages
expression, but I'm having a hard time finding out what the problem might be (since that wrapper works just fine for almost any other attribute set). Any suggestions how to remedy this issue are highly welcome.The text was updated successfully, but these errors were encountered: