|
We have an issue with an outlook addin that we dont have the source code for. It is a DLL that references some other DLL's. Under outlook it is listed as being mscoree (which is to be expected as it is a .Net app). How can we debug this? Is there a guide or document that I can use as a reference point? Previous experience is with SoftICE and VS 'attach to process', is reflector a similiar paradigm? Is there a better approach to what we are trying to do (determine why on some machines CPU usage goes up to 80% and outlook hangs). Thanks |
|
Reflector Pro works in the VS "attach to process" paradigm. You'd attach it to the failing process, find out which assemblies have been loaded, and then decompile and generate pdbs for these assemblies. They'd get loaded into VS and you'd be debugging through the managed code. By setting the symbol search path appropriately, you can get the microsoft symbols for the C++ parts of the runtime (like mscoree.dll), so you could at least see if the system is spending lots of time in some of the CLR support functionality. Personally, I'd attach VS studio and then hit break a few times and see what's on the call stack. With the appropriate symbols loaded, from the names you're likely to get a clue as to what it is doing. Then if it is managed, use Reflector to see the code that is running. If it is unmanaged, then at least check that the API is being passed the correct arguments. |
