Re: Elisp native profiler

[Stefan Monnier]

>> I'd guess it's because of the FIXME in profiler-call-tree-build-1.
>> I.e. you should be able to work around this limitation by increasing
>> profiler-max-stack-depth.
> Yes, looks more reasonable with 64 (vs default 16), see below.  Should
> the default be increased?

The problem is that it increases substantially the memory (and CPU) used
by the profiler.  I'd rather fix the FIXME, at which point we should be
able to use a much smaller value.


        Stefan