bug: segmentation fault nix build

[cchalc]

Are you following the right branch?

• My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• I have searched the existing issues

Issue description

I am getting a segmentation fault when trying to run a nix build with flakes.
[1] 88003 segmentation fault nix build .#C02CT8TEMD6M

It worked three weeks ago during my last change. I started tinkering around on another branch add_lvim which ended up giving me the segmentation fault. I tried switching back to main but I am still getting the same thing and I don't know how to debug it.

I have tried with GC_DONT_GC as indicated by @jonringer in this comment in Issue: Segmentation fault when building ISO image with nixFlakes #4246 but that did not work.

Maintainer CC

No response

System information

- system: `"x86_64-darwin"`
 - host os: `Darwin 21.6.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.6.0pre20211217_6e6e998`
 - channels(christopher.chalcraft): `"darwin, home-manager"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

[ncfavier]

If nix segfaults, that's an issue with nix, not home-manager. You should report the issue at nix, including a stack trace and/or a minimal reproducer.

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.