Track function start and ends for flame graphs
With this patch, and this file I called `log.py`: #!/usr/bin/env nix-shell #!nix-shell -i python3 -p python3 --pure import sys from pprint import pprint stack = [] timestack = [] for line in open(sys.argv[1]): components = line.strip().split(" ", 2) if components[0] != "function-trace": continue direction = components[1] components = components[2].rsplit(" ", 2) loc = components[0] _at = components[1] time = int(components[2]) if direction == "entered": stack.append(loc) timestack.append(time) elif direction == "exited": dur = time - timestack.pop() vst = ";".join(stack) print(f"{vst} {dur}") stack.pop() and: nix-instantiate --trace-function-calls -vvvv ../nixpkgs/pkgs/top-level/release.nix -A unstable > log.matthewbauer 2>&1 ./log.py ./log.matthewbauer > log.matthewbauer.folded flamegraph.pl --title matthewbauer-post-pr log.matthewbauer.folded > log.matthewbauer.folded.svg I can make flame graphs like: http://gsc.io/log.matthewbauer.folded.svg --- Includes test cases around function call failures and tryEval. Uses RAII so the finish is always called at the end of the function.
Showing
- contrib/stack-collapse.py 39 additions, 0 deletionscontrib/stack-collapse.py
- doc/manual/command-ref/conf-file.xml 28 additions, 0 deletionsdoc/manual/command-ref/conf-file.xml
- src/libexpr/eval.cc 6 additions, 2 deletionssrc/libexpr/eval.cc
- src/libexpr/eval.hh 4 additions, 0 deletionssrc/libexpr/eval.hh
- src/libexpr/function-trace.hh 24 additions, 0 deletionssrc/libexpr/function-trace.hh
- tests/function-trace.sh 86 additions, 0 deletionstests/function-trace.sh
- tests/local.mk 2 additions, 1 deletiontests/local.mk
Loading
Please register or sign in to comment