Just noticed something--in the ClassLoader::LoadTypeHandleFromToken method,
the call to the profiler indicating the start of class resolution occurs
*after* the attempt to load the type has already either succeeded or failed.
If a profiler is depending on this callback to know when to instrument a
class, it'll never do its work in time. (The two profiler callbacks, start
and finished, occur one right after the other.)
Relevant lines are clsload.cpp:1655-1673 (the #ifdef PROFILING_SUPPORTED
block).
Ted Neward
{.NET || Java} Course Author & Instructor, DevelopMentor
(http://www.develop.com)
http://www.javageeks.com/tneward
http://www.clrgeeks.com/tneward
