Bug 686543

Summary: Profiler loads on Mac OS X but does not produce any sensible report
Product: [Mono] Mono: Runtime Reporter: Christian Stümpel <mail>
Component: debugAssignee: Mono Bugs <mono-bugs>
Status: NEW --- QA Contact: Mono Bugs <mono-bugs>
Severity: Normal    
Priority: P5 - None    
Version: 2.10.x   
Target Milestone: ---   
Hardware: x86-64   
OS: Mac OS X 10.6   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Christian Stümpel 2011-04-11 07:46:02 UTC 
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16

With the DYLD_FALLBACK_LIBRARY_PATH set to mono's lib directory, I can get the profiler to load with:

mono --profiler Test.exe

where Test is a HelloWorld application or another, more complex exe.

The output I get is always almost empty: Loaded images is always reported 0, no calls nor thread info show up in the report.

When I try the same under Linux, the profiler works as described on the Mono website and produces the expected output.





Reproducible: Always

Steps to Reproduce:
1. mono --profiler HelloWorld.exe
2.
3.
Actual Results:  
Mono log profiler data
	Profiler version: 0.4
	Data version: 4
	Mean timer overhead: 292 nanoseconds
	Program startup: Mon Apr 11 09:38:26 2011
	Program ID: 21728

JIT summary
	Compiled methods: 0
	Generated code size: 0

GC summary
	GC resizes: 0
	Max heap size: 0
	Object moves: 0

Metadata summary
	Loaded images: 0

Exception summary
	Throws: 0

Thread summary


Expected Results:  
A profiler output
Comment 1 Miguel de Icaza 2011-04-16 23:52:23 UTC 
Paolo, could you look at this profiler failure on OSX?
Comment 2 Paolo Molaro 2011-04-19 16:19:29 UTC 
This looks like the symptoms of a miscompiled mono/profiler module: where is your mono and profiler coming from? Is it really the last 2.10.x? Because this issue has been fixed in december...
Comment 3 Christian Stümpel 2011-04-19 20:27:29 UTC 
(In reply to comment #2)
> This looks like the symptoms of a miscompiled mono/profiler module: where is
> your mono and profiler coming from? Is it really the last 2.10.x? Because this
> issue has been fixed in december...

It is the 2.10.x from the mono-project web site. I have never compiled mono myself. mono --version reports the following:

Mono JIT compiler version 2.10.1 (tarball Fri Feb 25 15:56:49 MST 2011)
Copyright (C) 2002-2011 Novell, Inc and Contributors. www.mono-project.com
	TLS:           normal
	SIGSEGV:       normal
	Notification:  Thread + polling
	Architecture:  x86
	Disabled:      none
	Misc:          debugger softdebug 
	LLVM:          yes(2.9svn-mono)
	GC:            Included Boehm (with typed GC)