Statprof uses stack trace buffer to always provide full stacks
authorAndy Wingo <wingo@pobox.com>
Fri, 28 Feb 2014 18:31:46 +0000 (19:31 +0100)
committerAndy Wingo <wingo@pobox.com>
Fri, 28 Feb 2014 18:31:46 +0000 (19:31 +0100)
commitcd073eb4a970eb77b3ef92d4a3e4daac4c8177dd
tree762f970c260f585b66d2d454bc932335db4fef81
parent3f9f4a2d59277a11805e5ce75738c59fc38f4ad4
Statprof uses stack trace buffer to always provide full stacks

* module/statprof.scm (<state>): Remove record-full-stacks? and stacks
  members.  The stack trace buffer is sufficient.
  (fresh-profiler-state): Adapt.
  (sample-stack-procs): Don't save stacks.
  (statprof-reset): Deprecate the full-stacks? argument.
  (stack-samples->procedure-data): Remove a needless vector-ref.
  (stack-samples->callee-lists): New helper.
  (statprof-fetch-stacks): Use stack-samples->callee-lists.
  (statprof-fetch-call-tree): Use stack-samples->callee-lists, and
  implement our own callee->string helper.
  (statprof, with-statprof, gcprof): Deprecate full-stacks? argument.
module/statprof.scm