> [...] > > The CorLoadXXX flags identify the various flavors of loading PE files > into memory. Rotor can't ever call LoadLibrary to load managed PE file > because of it is not portable. Thus, we have twisted the meaning of > these flags to avoid the LoadLibrary codepath, but we unfortunately > managed to break the profiler along the way. I won't try to describe the > meaning of the flags in Rotor since it is twisted and you will easily > find counter example to my explanation. > > [...]
Okay, thank you very much, that explains why I couldn't really figure it out by myself when scanning through the Rotor sources. Fabian
