Debugging native code called from managed code
-
This only works if I run the program outside the debugger, let it crash, then "manually select debuggers". If I do anything else, visual studio (2010 Pro, by the way) pretends that the call site of the native function is somehow at fault, unless the "exception" was a debug break, then it just closes the program being debugged. It's a little annoying to always have to let the program crash and then "manually select debuggers", is there anything I can do about that?
-
This only works if I run the program outside the debugger, let it crash, then "manually select debuggers". If I do anything else, visual studio (2010 Pro, by the way) pretends that the call site of the native function is somehow at fault, unless the "exception" was a debug break, then it just closes the program being debugged. It's a little annoying to always have to let the program crash and then "manually select debuggers", is there anything I can do about that?
harold aptroot wrote:
is there anything I can do about that?
Curse Microsoft?
The difficult we do right away... ...the impossible takes slightly longer.
-
harold aptroot wrote:
is there anything I can do about that?
Curse Microsoft?
The difficult we do right away... ...the impossible takes slightly longer.
-
I find invoking a "Chook" curse aimed at Microsoft works. How do I know this? I rang them one day and asked if they had and Chooks. They replied "No", so it must work!!
