This crashes on macOS.
For consistency, use the same version on all platforms.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: nix [69105]
Path: /Users/USER/*/nix
Identifier: nix
Version: ???
Code Type: ARM-64 (Native)
Parent Process: Exited process [69036]
Responsible: ghostty [609]
User ID: 501
Date/Time: 2025-03-24 10:28:36.3531 +0100
OS Version: macOS 15.1.1 (24B91)
Report Version: 12
Anonymous UUID: 43196E0E-30B7-6E8A-68F3-0C573FEA61E3
Sleep/Wake UUID: C4FFF3A0-095A-4AE0-935B-60B5E7DE7522
Time Awake Since Boot: 130000 seconds
Time Since Wake: 78381 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000010d7d3ff4
Exception Codes: 0x0000000000000001, 0x000000010d7d3ff4
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [69105]
VM Region Info: 0x10d7d3ff4 is not in any region. Bytes after previous region: 49141 Bytes before following region: 196620
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
__LINKEDIT 10d7c0000-10d7c8000 [ 32K] r--/rwx SM=COW /Volumes/VOLUME/*/liblowdown.1.dylib
---> GAP OF 0x3c000 BYTES
VM_ALLOCATE 10d804000-10d854000 [ 320K] rw-/rwx SM=PRV
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x10d7d3ff4 ???
1 libtbb.12.14.dylib 0x106abd4f8 tbb::detail::r1::__TBB_InitOnce::~__TBB_InitOnce() + 60
2 libsystem_c.dylib 0x1939f2998 __cxa_finalize_ranges + 476
3 libsystem_c.dylib 0x1939f275c exit + 44
4 libdyld.dylib 0x193b5a94c dyld4::LibSystemHelpers::exit(int) const + 20
5 dyld 0x1937b42c8 start + 2924
Thread 1:
0 libsystem_pthread.dylib 0x193b320e8 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x193b320e8 start_wqthread + 0
Thread 3:
0 libsystem_kernel.dylib 0x193b01840 __sigwait + 8
1 libsystem_pthread.dylib 0x193b37a9c sigwait + 40
2 libnixutil.dylib 0x106fae034 nix::signalHandlerThread(unsigned int) + 36 (signals.cc:62)
3 libnixutil.dylib 0x106fb0730 decltype(std::declval<void (*)(unsigned int)>()(std::declval<unsigned int>())) std::__1::__invoke[abi:fe190107]<void (*)(unsigned int), unsigned int>(void (*&&)(unsigned int), unsigned int&&) + 40 (invoke.h:149)
4 libnixutil.dylib 0x106fb06f4 void std::__1::__thread_execute[abi:fe190107]<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (*)(unsigned int), unsigned int, 2ul>(std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (*)(unsigned int), unsigned int>&, std::__1::__tuple_indices<2ul>) + 48 (thread.h:192)
5 libnixutil.dylib 0x106fb0340 void* std::__1::__thread_proxy[abi:fe190107]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (*)(unsigned int), unsigned int>>(void*) + 100 (thread.h:201)
6 libsystem_pthread.dylib 0x193b372e4 _pthread_start + 136
7 libsystem_pthread.dylib 0x193b320fc thread_start + 8
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x000000010dc8bf80 x1: 0x000000010d7d3ff4 x2: 0x0000000000000103 x3: 0x00000001f9b12978
x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000
x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x000000016b68dc40 x11: 0x000000016b68ded0
x12: 0x0000000000000000 x13: 0x0000000000018000 x14: 0x0000000000004af0 x15: 0x00000001111477df
x16: 0x0000000193b693b4 x17: 0x0000000200eaa590 x18: 0x0000000000000000 x19: 0x0000000106af0838
x20: 0x0000000106af0388 x21: 0x0000000000000002 x22: 0x0000000106158030 x23: 0x0000000000000000
x24: 0x0000000000000008 x25: 0x00000001f8c54000 x26: 0x0000000000000004 x27: 0x0000000000000003
x28: 0x0000000000000003 fp: 0x000000016b68f7a0 lr: 0x0000000106abc110
sp: 0x000000016b68f790 pc: 0x000000010d7d3ff4 cpsr: 0x60001000
far: 0x000000010d7d3ff4 esr: 0x82000007 (Instruction Abort) Translation fault
Nixpkgs is a collection of over 100,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.
Manuals
- NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
- Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
- Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools
Community
- Discourse Forum
- Matrix Chat
- NixOS Weekly
- Official wiki
- Community-maintained list of ways to get in touch (Discord, Telegram, IRC, etc.)
Other Project Repositories
The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:
- Nix - the purely functional package manager
- NixOps - the tool to remotely deploy NixOS machines
- nixos-hardware - NixOS profiles to optimize settings for different hardware
- Nix RFCs - the formal process for making substantial changes to the community
- NixOS homepage - the NixOS.org website
- hydra - our continuous integration system
- NixOS Artwork - NixOS artwork
Continuous Integration and Distribution
Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.
- Continuous package builds for unstable/master
- Continuous package builds for the NixOS 24.11 release
- Tests for unstable/master
- Tests for the NixOS 24.11 release
Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.
Contributing
Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.
Community contributions are always welcome through GitHub Issues and Pull Requests.
For more information about contributing to the project, please visit the contributing page.
Donations
The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.
You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:
License
Nixpkgs is licensed under the MIT License.
Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.