From 27000467387970cc4f75a391e7805219265d5836 Mon Sep 17 00:00:00 2001 From: Paolo Molaro Date: Mon, 8 Nov 2010 15:16:03 +0100 Subject: [PATCH] More log profiler doc clarifications. --- mono/profiler/log-profiler.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/mono/profiler/log-profiler.txt b/mono/profiler/log-profiler.txt index b21d2588c3b..0b9e8761f54 100644 --- a/mono/profiler/log-profiler.txt +++ b/mono/profiler/log-profiler.txt @@ -99,7 +99,7 @@ MODE can be one of: * *fast*: a usually faster but possibly more inaccurate timer * *maxframes=NUM*: when a stack trace needs to be performed, collect *NUM* frames -at the most. +at the most. The default is 8. * *calldepth=NUM*: ignore method enter/leave events when the call chain depth is bigger than NUM. @@ -142,7 +142,10 @@ The maximum number of methods in each stack trace can be specified with the The stack trace info will be available if method enter/leave events have been recorded or if stack trace collection wasn't explicitly disabled with the -*maxframes=0* option. +*maxframes=0* profiler option. Note that the profiler will collect up to 8 +frames by default at specific events when the *nocalls* option is used, so +in that case, if more stack frames are required in mprof-report, a bigger +value for maxframes when profiling must be used, too. ### Sort order for methods and allocations -- 2.25.1