Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Interop (mixed-... » Design   (RSS)
Wednesday, February 09, 2005 8:55 PM

Hardmode vs. Softmode

User-mode debugging can be split into 2 models: Hardmode and Softmode. Hardmode means using the native debugging APIs. This means all threads are stopped by the OS at each debug event and there’s no helper-thread . The debugger does not need to run any
Posted by jmstall | 5 Comments
Friday, January 28, 2005 12:24 AM

What is Interop-Debugging?

(This is an excerpt from an internal document I wrote explaining what is Interop-Debugging (aka Mixed Mode) and how does it work under the covers) General Debugging background. When a process is being debugged, it generates debug-events which a debugger
Posted by jmstall | 9 Comments
Wednesday, October 13, 2004 1:18 PM

Implications of using a helper thread for debugging

What it means? I mentioned in a previous post ( http://blogs.msdn.com/jmstall/archive/2004/10/10/240452.aspx ) that the CLR debugging services is an “in-process model” which means it has a helper thread running in the same process as the EE which provides
Posted by jmstall | 14 Comments
Sunday, October 10, 2004 12:49 PM

Why is managed debugging different than native-debugging?

People ask “why can’t a native debugger debug managed code?”. The reason is that the CLR provides a lot of cool services beyond what you get in a typical native C++ app, such as: running on a Virtual Machine / JITing, Dynamic class layout, the type-system,
Posted by jmstall | 10 Comments
 
Page view tracker