Currently, Mdbg as a de**** does not have JMC support. But it includes managed wrappers that would allow somebody to add JMC support (eg, in an extension or future version)
"Does the ICorDebugStepper2 interface need to be used to support JMC" Yes. More on actually using ICorDebug for JMC is here: http://www.hide-link.com/ , and http://www.hide-link.com/
More specifically Mdbg has multiple layers: 1) "Wrappers": There are the managed wrappers for ICorDebug a) that includes the raw ICorDebug imports, b) and the managed wrappers that smooth out the warts in the raw ICorDebug imports. These are the Cor* wrappers. This has very little policy. 2) "Engine". This has a lot of additional functionality (eg, symbol support, naming resolution, etc). This is the Mdbg* stuff (like MdbgProcess.cs). 3) "De****/Shell": And then there's the actual de**** / shell that builds on the engine / wrappers.
Ideally, all of the COM-classic ICorDebug has been wrapped in the in Cor* functions ("The wrappers"); but that doesn't mean that "MDbg the De****" uses it all.
|