[Mono-list] Profiling is not working?

fsmac yves at mindset-media.com
Thu Aug 20 18:19:44 EDT 2009

Thanks Rodrigo.

On Linux (CentOS 5.3, with mono- and mono-tools 2.4.2 compiled from
sources), statistical profiling still does not seem to work. If I run

    % mono --profile=logging:s MyApp.exe ....

I get totally random errors in MyApp.exe, from Directory.FileExists() saying
files that are there do not exist, to crashing in FSharp type initialization
code, to just SIGABRT. Is that a known issue?

It seems like logging:c allows my app to run as intended and I am trying
this right now, though this is much much slower.


PS: mono-tools didn't compile fully, with GDI errors compiling gendarme
(adding a .png into a res file) and some other GLib exception (missing an
exception type), but mprof-decoder did compile properly, and the profiler
itself is in the main mono source tree, right?

Rodrigo Kumpera wrote:
> Profiling is only supported on linux.
> The default profiler is not recommended on recent versions of mono (2.4 or
> trunk),
> please try the new logging profiler[1], which have a work-in-progress
> GUI[2]
> for it.
> Keep in mind that under statistical profiling you need to run a long
> enough
> program
> to get enough samples and build a meaningful result. Usually 1-15 minutes
> of
> steady
> state execution is enough to capture enough information.
> The new statistical profiler returns information of managed and unmanaged
> code
> mixed together so if you get a result with too many frames from the mono
> runtime
> I can give you a hand on figuring out the problem if I get access to the
> sampling file.
> Cheers,
> Rodrigo

View this message in context: http://www.nabble.com/Profiling-is-not-working--tp24834274p25071147.html
Sent from the Mono - General mailing list archive at Nabble.com.

More information about the Mono-list mailing list