[Nix#8880] Regression: nix-shell
crashes #123
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#123
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upstream-Issue: NixOS/nix#8880
Describe the bug
Starting with nix 2.16,
nix-shell
on macOS crashes withBus error: 10
during the evaluation stage.Bisecting identified this commit as the first commit where this crash happens:
94812cca98
Steps To Reproduce
Example project:
example.zip
Run
nix-shell
without argumentsSee error
Expected behavior
nix-shell
does not crash during the evaluation stage, downloads the dependencies and in this particular example, fails with Python-related errors.Additional context
Segmentation fault (core dumped)
occurs on Linux as wellPriorities
Add 👍 to issues you find important.
still reproduces as a stack overflow here.
This is actually causing the daemon to dump core, very interestingly:
Simpler reproducer:
doesn't crash under Rosetta on aarch64-darwin, though it doesn't actually enter the shell either
n.b. the daemon crash is a red herring. we double throw if the protocol disconnects leading to core dump as above, but that is not the bug here. It's the client stack overflow that is.
Daemon no longer dumps core as of 2.92-dev! This is still a bug that there is infinite recursion, but it's a different bug.