Managed vs. Native debugging APIs

re: Managed vs. Native debugging APIs

barrkel — Tue, 04 Jul 2006 07:00:40 GMT

On the topic of debuggers not changing behaviour, is there any chance of a change on the WinForms debugging front any time soon?

Currently, debugging a managed app using WinForms causes gunk to be inserted into the message handling call stack, which changes how exceptions get propagated from event handlers. Caused me no end of grief. I had to rearchitect the UI exception handling in order to make the app sanely debuggable.

re: Managed vs. Native debugging APIs

Sameer V. — Tue, 04 Jul 2006 12:27:09 GMT

Hi Mike,

wow, you are working on native debugger on managed code. I hope you will be sharing your experiences with us!!

I've been trying to do this for sometime. but as I'm not a C++ guy. my PInvoke signatures were never right.
Just out of curiocity r u using Kernel32 API or Dbgeng.dll

How about 64bit?

Good luck

Sameer

re: Managed vs. Native debugging APIs

jmstall — Fri, 07 Jul 2006 07:02:38 GMT

Barrkel - that problem with winforms is notorious and a text book example of the "No changing behavior" rule. I'd like to see it become an MDA instead. I don't know when it will be fixed.

Experiences with FxCop and wrapping the native debug API

Mike Stall's .NET Debugging Blog — Wed, 12 Jul 2006 08:55:10 GMT

I'm writing some managed wrappers for the native-debugging API (I expect they'll eventually become part...

Caveats about managed JIT-debugging

Mike Stall's .NET Debugging Blog — Mon, 24 Jul 2006 18:15:49 GMT

I received some questions in the mailbag about what Debugger.Launch actually does. Debugger.Launch the...

Debugger.Break()

Mike Stall's .NET Debugging Blog — Wed, 03 Oct 2007 08:32:42 GMT

System.Diagnostics.Debugger.Break() is a BCL method that causes a program to issue a User Breakpoint