How do we capture each method invocation and return? Is it possible to
capture its information as well?
Thank you very much.
===
This list is hosted by DevelopMentor® http://www.develop.com
NEW! ASP.NET courses you may be interested in:
2 Days of ASP.NET, 29
Take a look at the profiler, in sscli\samples\utilities\dnproprofiler.
There is a dnprofiler.html that describes a bit about the profiler
interface. You should be able to use the JITCOmpilationStarted()
callback to instrument each method's IL as it is jitted.
Barry
This posting is provided AS IS
The CProfilerCallBack::JITCompilationStarted function only displays the
method name that is being jitted.
if ( GetMethodNameFromFunctionId( functionId, wszClass, wszMethod ) )
{
ProfilerPrintf(JITCompilationStarted: %ls::%ls\n,wszClass,wszMethod);
}
else
{
ProfilerPrintf(
After peering at rotor for a while, it seems that if COM exists on the
platform, you could write an alternate PAL that took advantage of the
native COM. It seems that you could get interop out of rotor into COM
objects that way. However, I'm also interested in hosting the rotor
runtime by a native
You could host Rotor in-process inside a native app using the same
mechanism that clix.exe uses: call Win32 LoadLibrary() on mscoree.dll,
then GetProcAddress for _CorExeMain2 and call it. You *might* need to
first call LoadLibrary() on rotor_pal.dll and call its PAL_Initialize()
before loading
The problem you are seeing is caused by optimization settings. The
default Rotor build flavor is fastchecked: both optimizations and
debugging instrumentation are turned on.
Try using the checked build flavor of Rotor. Setup the environment by
running env.bat checked and then do buildall as
Check Rewrite MSIL Code on the Fly with the .NET Framework Profiling
API article on MSDN:
http://msdn.microsoft.com/msdnmag/issues/03/09/NETProfilingAPI/default.a
spx . It should have answers to all your questions.
Note that there is bug in the profiler implementation in the final Rotor
v1
