search

shekharpro / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

MbUnit Native Debugging #431

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Some of our test suites call into Native code, but we cannot step into the
native code when using the new debug command line or button in Icarus. 

Attached is a patch for Gallio.VisualStudio.Interop.VisualStudioDebugger.

You will also need to add a reference to EnvDTE80 to the
Gallio.VisualStudio.Interop project (and the vs2010 project). I have
attached a patch for the vs2008 project file, but I am always wary about
patching Visual Studio solution and project files...

Original issue reported on code.google.com by rpro...@gmail.com on 22 Apr 2009 at 7:55

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks!

After thinking about it some more, I've decided to commit this patch more or 
less
as-is even though there may be circumstances where we would prefer not to enable
Native debugging.  Supporting a configurable set of debugger options can be 
another
feature we implement later.

Original comment by jeff.br...@gmail.com on 27 Apr 2009 at 5:42

GoogleCodeExporter commented 8 years ago

Original comment by jeff.br...@gmail.com on 29 Jun 2009 at 8:33

GoogleCodeExporter commented 8 years ago 
Half-done.

When we attach to existing processes, we now pass in the Managed and Native 
debugger
engines.  However when we launch new processes with the debugger we only use 
Managed
because Visual Studio is crashing when I try to pass in the required engine 
GUIDs. 
Since we are most often launching new processes, this feature doesn't quite 
work yet.

I could use a hand figuring out why this is crashing.  The relevant code is in
VisualStudioDebugger.LaunchProcess in Gallio.VisualStudio.Interop.

Original comment by jeff.br...@gmail.com on 31 Jul 2009 at 3:59

GoogleCodeExporter commented 8 years ago

Original comment by jeff.br...@gmail.com on 29 Sep 2009 at 7:21