Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Automatic Breakpoint at void loop() (Read 4480 times)
James Brown
Junior Member
**
Offline


Posts: 46
Location: Near San Diego
Joined: Jul 31st, 2012
Automatic Breakpoint at void loop()
Sep 8th, 2013 at 2:55pm
Print Post  
Tim - In todays release I see a breakpoint is automatically inserted at my void loop() instruction.  It is:
'break when the hit count is a multiple of 250'
I can disable it and everything works as expected but is it necessary?
Regards..... Jim
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Automatic Breakpoint at void loop()
Reply #1 - Sep 8th, 2013 at 5:16pm
Print Post  
Hi James,

We hope to extend the documentation during the coming days/week. 

At the moment only the "New Release (1309.04)" notes in this forum and the release notes on our codeplex download site explain about the new auto breakpoint facility (and other things)

The automatic breakpoint is inserted for new users who struggle to learn Arduino at the same time as learning the debugger. As you correctly point out an example breakpoint is created in the loop which reports at 4hz (250ms) and has a number of properties set such as "Condition", "Hit Count", "When Hit".

The example breakpoint is only created if you have not created your own breakpoint(s) for the current project and if the debugger is switched on.

This auto creation of a breakpoint for new users also means the debugger needed to be switched on automatically, when in previous versions the debugger was enabled manually in the project properties (Micro Debug=Full)

So there are actually two automatic tasks happening in 1309.4 that did not happen in previous versions of Visual Micro which means that when you click "Debug>Start" in Visual or Atmel Studio. 1) Debug is Enabled and 2) An example  BreakPoint is created in the loop()

Both of these automatic tasks can be switched off using Tools>Options>Visual Micro

1) "Always use debugger" - Defaults to true, change it to False to revert to manual control of debug via the project properties (Micro Debug=Full)

2) "loop - Auto Create Breakpoint" - Defaults to true, change it to False to prevent auto creation of a breakpoint as described.

Obviously 2) does not happen if the debugger is not active or if you select "Debug>Start without debugging". 

It might also be useful to note that once the example breakpoint has been created it is never automatically removed or modified by Visual Micro. You have full control over the breakpoint which means it can be modified or deleted as required (or not).

Sorry for the verbose answer but it is an important change that many others will also question. So the more info the better (I hope).

Thanks for raising the question
« Last Edit: Sep 8th, 2013 at 5:27pm by Tim@Visual Micro »  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint