Visual Studio Ide for Arduino
https://www.visualmicro.com/forums/YaBB.pl
Visual Micro >> Visual Studio 2012, 2013, 2015, 2017 >> Debug: Stop execution, and as soon as I close the dialog, the action gets reset to continue executio
https://www.visualmicro.com/forums/YaBB.pl?num=1552937056

Message started by Todd Osborne on Mar 18th, 2019 at 7:24pm

Title: Debug: Stop execution, and as soon as I close the dialog, the action gets reset to continue executio
Post by Todd Osborne on Mar 18th, 2019 at 7:24pm
I am using Visual Studio 2017 and targetting Teensy 3.2. Thanks. Seems I can no longer debug . I set a breakpoint, set the action to stop execution, and as soon as I close the dialog, the action gets reset to continue execution. The breakpoint is hit, but does not stop execution, rendering the debugging essentially useless.

Title: Re: Debug: Stop execution, and as soon as I close the dialog, the action gets reset to continue executio
Post by Visual Micro on Mar 23rd, 2019 at 6:32pm
Visual Micro does not change or manage breakpoints other than adding the demo breakpoint if one does not exist and if tutorial mode is enabled.

In essence the breakpoint system is entirely a VS2017 c++ feature. I haven't heard of this issue before but they are making a lot of fixes and changes for VS2017 therefore please ensure you are on an update to date version and if that doesn't fix it try a repair of vs.

Out of interest. Can you confirm you are not debugging during the change of break-point properties?

Title: Re: Debug: Stop execution, and as soon as I close the dialog, the action gets reset to continue executio
Post by Todd Osborne on Mar 25th, 2019 at 1:14pm
No, not trying to change breakpoints during debugging. I know VS is different than normal debugging and that breakpoints can only be set before upload.

Title: Re: Debug: Stop execution, and as soon as I close the dialog, the action gets reset to continue executio
Post by Visual Micro on Mar 25th, 2019 at 1:19pm
Thanks, okay sounds like a visual studio bug. Ensure on the latest release of vs2017 and run a repair.

If that fails please confirm if the issue happens in a new project. If the new project is okay then we need to look at the files of your current project. If I recall vs puts breakpoints in the .sln but I am sure it would only save changes when closing the solution therefore can't be a readonly/permissions issue.

It's a strange one, hopefully the repair fixes but bear in mind that Visual Micro doesn't know if the dialog is open or not. Do you have same problem if you "right click the breakpoint > action", that uses the inplace breakpoint editor instead of dialog.


Visual Studio Ide for Arduino » Powered by YaBB 2.5.2!
YaBB Forum Software © 2000-2019. All Rights Reserved.