You must set your dynamic library path.
This works on OSX:
LD_LIBRARY_PATH=/Library/Frameworks/Mono.framework/Versions/Current/lib
mono --profile=log:calls hello.exe
On Tue, Mar 19, 2013 at 9:45 AM, Jonathan Shore wrote:
> I just did a new build of mono with llvm of the mono-3.0.7 tar ball.
I just did a new build of mono with llvm of the mono-3.0.7 tar ball. I get
the same problem with mono-sgen:
$ /opt/mono-3.0/bin/mono-sgen
--profile=log:calls,output=profile.log,maxframes=10,calldepth=100
EAOutputEvaluator.exe ...
The 'log' profiler wasn't found in the main executable nor coul
I believe the GC related profiling options, like allocation tracking
or heap-shot, only work with sgen. The performance related options
work irrespective of the GC being used.
Alan
On 18 March 2013 23:17, Andres G. Aragoneses wrote:
> On 18/03/13 22:57, Esben Laursen wrote:
>>
>> Den 18-03-2013
On 18/03/13 22:57, Esben Laursen wrote:
Den 18-03-2013 20:59, Jonathan Shore skrev:
Hi,
I've used mono --profile… in the past with 2.10.x and did not have
problems in being able to run.I was trying to run profiling on an
app again, this time with 3.0.x. On both osx and linux, I get:
The
Den 18-03-2013 20:59, Jonathan Shore skrev:
Hi,
I've used mono --profile... in the past with 2.10.x and did not have
problems in being able to run.I was trying to run profiling on an
app again, this time with 3.0.x. On both osx and linux, I get:
The 'log' profiler wasn't found in the m
Hi,
I've used mono --profile… in the past with 2.10.x and did not have problems in
being able to run.I was trying to run profiling on an app again, this time
with 3.0.x. On both osx and linux, I get:
The 'log' profiler wasn't found in the main executable nor could it be loaded
from 'mono
