|
https://developercommunity.visua ... n-ccli-project.html
I have several C++/CLI projects, and I've recently upgraded to VS2017. Now whenever I launch the debugger I'm unable to hit any breakpoints, I get a "The breakpoint will not currently be hit. No executable code of the debugger's target code type is associated with this line. Possible causes include: conditional compilation, compiler optimizations, or the target architecture of this line is not supported by the current debugger code type."
If I change the debugger type to Mixed, then I get an error "Unable to start program 'c:\my\program.exe' Mixed-mode debugging is not supported with the legacy managed debug engine."
What's it take to debug C++/CLI code in VS2017?
[size=11.844px]Best Solution
For me, the solution was to checked Options=>Debugging=>General=>Suppress jit optimization on module load After this, I am able to debug my C++/CLI project.
评论 [url=] 隐藏 1[/url] · 分享
Mark Douglas· 02月02日 12:44 1
Thank you! This solved the problem for me after scratching my head for a while. Why is this option on by default if it means you can't set breakpoints correctly in managed C++ code? Surely it should default to disabled!
|
|