6 ms·
Nix has a debugger now. You can drop into the frames that are causing problems and inspect the state. Miles easier than looking at the trace manually.
by geddawm 4y ago
Nix has a debugger now. You can drop into the frames that are causing problems and inspect the state. Miles easier than looking at the trace manually.
- benreesman 4y agoI last flashed my flake.lock in June, so I might be out of date, but my rigs can’t reliably include the line number in my code that led to the duck-typing fiasco deep in the core of someLanguage.withPackages.fuck.WTF.this. Fix the fucking “—show-trace” thing folks. Seriously.
- VTimofeenko 4y agoOut of all cases when I used --show-trace, I can remember it being useful only once or twice. I gave up and just sprinkled builtins.trace. IIRC debugger comes with nix 2.9 and nixpkgs for 22.05 still has 2.8.x.
- n8henrie 4y agoI was excited to see the debugger flag to nix build the other day, since I'm really struggling cross-compiling an RPi on BTRFS root sd image. Of course running with the debugger flag resulted in an unintelligible error message and no debugger.
- rtpg 4y agoAny link to documentation on how to use it? Would be a godsend for me