CLI --help
crashes with SIGBUS (Misaligned address error) #787
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#787
Loading…
Add table
Add a link
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?
Describe the bug
All my attempts to show CLI help crash with
SIGBUS
.Steps To Reproduce
nix --help
, or any subcommand also seems to reproduce (e.g.nix flake --help
).Expected behavior
Normal help output is displayed, no crash
nix --version
outputAdditional context
nix.conf
Lix-module
I am using the
lix-module.overlays.default
withnix-darwin
plus a small custom overlay to disable some tests that kept failing:Lix flake inputs
lldb backtrace
Strange behavior
To check if it was just an old version bug, I tried running a new Lix version to see if its
--help
worked, and it did, but somehow this also seems to have resolved my original issue???2.93.0-dev-pre20250401-5a7e9e1
with--help
(it works)2.93.0-dev-pre20250316-2a33681
with--help
(previously failing, now working)This seems very odd to me and I can't be sure what's happening, but it suggests maybe this issue is not actually as reproducible as I first thought... also perhaps upgrading will resolve it in the general case so maybe there's nothing really to do here.
Hi there, can you retry with the released 2.93.0 or recent HEAD? I do not have a handy macOS so it's hard for me to reproduce.