New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
valgrind: enable debug info #47251
valgrind: enable debug info #47251
Conversation
Please move this to the staging branch. |
@Mic92 done |
At least on ARM, valgrind produces no stack trace unless debug info is available for its own libraries.
9b5041d
to
8a30fe3
Compare
Wait, so does setting |
It is possible that we do not have this yet for macOS. I think I read something on those lines. |
If that is the case, it seems like it should just be automatically disabled for macOS, rather than requiring each package to disable it. |
true. |
@GrahamcOfBorg build valgrind |
Timed out, unknown build status on x86_64-darwin (full log) Attempted: valgrind Partial log (click to expand)
|
Timed out, unknown build status on x86_64-linux (full log) Attempted: valgrind Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: valgrind Partial log (click to expand)
|
Motivation for this change
At least on ARM, valgrind produces no stack trace unless debug info is available for its own libraries.
Also, anyone who tries to use valgrind on NixOS should be aware that the option
--extra-debuginfo-path
does not work with.build-id
debug files like NixOS uses, so until that is fixed, the only way to use valgrind on NixOS is to symlink the debug info directory to/usr/lib/debug
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)