i try to use CLR Profiler v2.0 sample from MSDN to profiling managed windows form apps , always throw exception.

exception text is:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at WindowsApplication1.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()

The profiler sample is from "No Code Can Hide from the Profiling API in the .NET Framework 2.0". I build the dll, then use command line to regsvr.

thanks!

I verified that I'm executing through FunctionEnterNaked2 without problems. My guess is we may be executing different versions of the runtime. If you'd like to probe deeper, here are a couple things you can do to help:

1) Get a full stack trace at the point of the exception, including all unmanaged code. You'll want to ensure your debugger is connecting to the Microsoft symbol server to ensure you're getting all the symbols for the runtime: http://msdl.microsoft.com/download/symbols.

2) Verify which versions of mscorwks.dll / mscordbc.dll are getting loaded. Using a debugger, detect the full path of the versions of those DLLs getting loaded, and check their version info in Windows Explorer.

Hello! I went to http://msdn.microsoft.com/msdnmag/issues/05/01/CLRProfilerand downloaded the profiler to try this out (please verify that's the same profiler you used). I then went to a command-prompt and did the following:

regsvr32 Profiler.dll

set COR_PROFILER={18884ADE-B15B-4af8-BE6C-FE5117BA4B32}

set COR_ENABLE_PROFILING=1

Thanks Dave

I just unpack the CLR Profiler.rar, there is a compiled dll in debug folder. I use it in command prompt to profile a win forms app, no modification to the code. Then exception.

Then I compile the profiler to release version, (project file is converted from vs8 to vs9), still exception.

But i find the key maybe:

m_dwEventMask |= COR_PRF_MONITOR_ENTERLEAVE;
dwFooMask += COR_PRF_MONITOR_ENTERLEAVE;

When I delete EnterLeave mask, there's no exception. Maybe the reason is inline asm code for ENTERLEAVE function?

I verified that I'm executing through FunctionEnterNaked2 without problems. My guess is we may be executing different versions of the runtime. If you'd like to probe deeper, here are a couple things you can do to help:

1) Get a full stack trace at the point of the exception, including all unmanaged code. You'll want to ensure your debugger is connecting to the Microsoft symbol server to ensure you're getting all the symbols for the runtime: http://msdl.microsoft.com/download/symbols.

2) Verify which versions of mscorwks.dll / mscordbc.dll are getting loaded. Using a debugger, detect the full path of the versions of those DLLs getting loaded, and check their version info in Windows Explorer.