From da18634eff4d8a49e9105c84b15dd139c47c1fc1 Mon Sep 17 00:00:00 2001 From: Ben Wolsieffer Date: Mon, 24 Sep 2018 16:57:38 -0400 Subject: valgrind: enable debug info (#47251) At least on ARM, valgrind produces no stack trace unless debug info is available for its own libraries. --- pkgs/development/tools/analysis/valgrind/default.nix | 1 + 1 file changed, 1 insertion(+) (limited to 'pkgs/development/tools/analysis/valgrind/default.nix') diff --git a/pkgs/development/tools/analysis/valgrind/default.nix b/pkgs/development/tools/analysis/valgrind/default.nix index 5734a0f2795..ccc2cf9b4ab 100644 --- a/pkgs/development/tools/analysis/valgrind/default.nix +++ b/pkgs/development/tools/analysis/valgrind/default.nix @@ -17,6 +17,7 @@ stdenv.mkDerivation rec { buildInputs = [ perl gdb ] ++ stdenv.lib.optionals (stdenv.isDarwin) [ bootstrap_cmds xnu ]; enableParallelBuilding = true; + separateDebugInfo = stdenv.isLinux; preConfigure = stdenv.lib.optionalString stdenv.isDarwin ( let OSRELEASE = '' -- cgit 1.4.1