3

After Google the issue i found that it was reported already but nothing useful yet from MS. I wonder if any one found a work around it?

JaredPar
  • 733,204
  • 149
  • 1,241
  • 1,454
UshaP
  • 1,271
  • 2
  • 18
  • 32
  • 2
    VS2010 hangs and crashes a lot – AJG85 Jul 19 '11 at 16:29
  • Only for c++. i have been using it intensively for c# and I'm very happy with it. – UshaP Jul 19 '11 at 17:37
  • 99% of my use is C++ ... I don't know what they did but it's horrid. Have you tried using a remote debugger or another instance of visual studio and attaching to the process? – AJG85 Jul 19 '11 at 20:21

3 Answers3

2

Another option is to use windbg. You'll have to do a lot of commands by hand, but it's the best debugger out there. It handles mixed mode without any major issues. It has a bit of a learning curve, but it's very versatile.

Zipper
  • 7,034
  • 8
  • 49
  • 66
1

Visual Studio's debugger is really not reliable when debugging mixed mode applications. Taken from my answer here #5965771:

  • If you're trying to debug a piece of native code try to use a native project as the debugger start-up application. Under the project settings, "Debugging" tab set the "Debugger Type" to "Mixed", for us this helped sometimes (the native project can be a DLL for example, simply set your main Exe as debugging target in the project settings);

OR, as already mentioned in another answer: Use WinDbg! With it you can debug both managed/unmanaged mixed code applications much more reliably.

Community
  • 1
  • 1
floyd73
  • 1,240
  • 9
  • 12
-1

use a different debugger, or don't use the debugger at all, just trace to a file or insert breakpoints in the code with inline assembly language.

marinara
  • 538
  • 1
  • 5
  • 10