6

I am debugging a very deep call stack. Unfortunately profiler reports (produced with M-x profiler-report) have a fixed width that obscures critical information when the stack gets deep.

enter image description here

Is there any way I can give myself some extra room?

PythonNut
  • 10,363
  • 2
  • 30
  • 76
  • 3
    These two variables look interesting, but I'm not sure they are what you need: profiler-report-cpu-line-format and profiler-report-memory-line-format The function profiler-format uses the words width and align, so that also looks interesting. – lawlist Jan 14 '15 at 05:50

1 Answers1

4

setf the caar of profiler-report-cpu-line-format and profiler-report-memory-line-format to a larger width (default 50 and 55). It'll take effect on subsequent runs of profiler-report. (Thanks lawlist's comment for pointing out these variables.)

(setf (caar profiler-report-cpu-line-format) 80
      (caar profiler-report-memory-line-format) 80)
Kisaragi Hiu
  • 315
  • 1
  • 6
  • 1
    Not just subsetquent runs of profiler report, but also the next time you expand a call in the current profile report (at least in my experience). The columns will become misaligned, but at least you'll be able to see the full function definition. – Alexey Shiklomanov Nov 01 '19 at 16:16