Why does switching debugging to native only mode crash my code in mscorlib.ni.dll? C++ VS2017

0

I am working on a VS2017 solution that builds a windows win32 application. I am using Windows 10. By inspection it appears to be one C++ "Form" application with a number of c++ libraries. I can debug the application fine using debug mode "auto". I have an issue and would like to use a "data breakpoint". If I change the debug mode form "auto" to "native only" the application "crashes" very early in its startup with an Exception

"Exception thrown at 0x72C48CD5 (mscorlib.ni.dll) in MC400Simulator.exe: 0xC0000005: Access violation reading location 0x00000008."

UPDATE: The exception can be ignored and pressing continue enough times gets me through it to running code and also the ability to set a data breakpoints.

Can I fix this so that I get "data breakpoints" working for at least one of the C++ libraries?

Ideas so far...

Would disabling debugging for all but the library I am interested in fix this issue?

Can you explain the crash, this may help me fix the issue?

Is this issue likely to be specific to loading this DLL? Knowing this could help find a solution.

Is the version of this DLL relevant to fixing this issue?

c++
forms
visual-studio
debugging
exception
asked on Stack Overflow Jul 4, 2018 by William J Bagshaw • edited Jul 4, 2018 by William J Bagshaw

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0