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 small bug: trace points in commented code (Read 5481 times)
Jürgen Hofmann
Newbies
*
Offline


Posts: 9
Joined: Jun 7th, 2013
small bug: trace points in commented code
Jun 7th, 2013 at 11:45am
Print Post  
Hi,

I think I found a small bug:

if you comment out code, that still has trace points set, they will be executed although the underlying code is not executed. One has to explicitly disable or delete the trace points and recompile.

Nevertheless: great product!

Jürgen
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: small bug: trace points in commented code
Reply #1 - Jun 7th, 2013 at 12:55pm
Print Post  
Thanks,

Yes because we inject serial.print statements for breakpoints you can put a BreakPoint on empty and commented lines and they will still work. 

All comments are converted to spaces when making a debug compile which avoids the need for the injection system to be concerned with them.


This is quite useful for new users but a little strange or confusing for experienced.

We are listening to feedback to decide if this should be allowed or now. It's not an easy decision  Smiley
  
Back to top
IP Logged
 
Jürgen Hofmann
Newbies
*
Offline


Posts: 9
Joined: Jun 7th, 2013
Re: small bug: trace points in commented code
Reply #2 - Jun 7th, 2013 at 1:46pm
Print Post  
Thanks for the fast reply!

To be honest, I would even find it confusing for beginners, because commented code should not produce any side effects.

Another point is that I frequently use #ifdefs for different builds and testing configurations. So if I #ifdef out a test routine, it will still produce the debug output which may slow down my programm...

But that are just my 2 cents...
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: small bug: trace points in commented code
Reply #3 - Jun 7th, 2013 at 2:24pm
Print Post  
Valid points but if a new user has an empty function, adds a breakpoint then runs the debugger they still get to see that the function is hit.

However maybe can have a half way solution? Breakpoints on comments should be ignored, breakpoints on empty code lines can be executed?

As concerns the #define, the breakpoint should be ignored by the compiler as normal?

Thanks
  
Back to top
IP Logged
 
Jürgen Hofmann
Newbies
*
Offline


Posts: 9
Joined: Jun 7th, 2013
Re: small bug: trace points in commented code
Reply #4 - Jun 10th, 2013 at 9:34am
Print Post  
Your suggestions sound very reasonable to me!

Thanks

Jürgen
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: small bug: trace points in commented code
Reply #5 - Jan 10th, 2015 at 10:11pm
Print Post  
Wow that was a long time. sorry!

This is implemented in the next service pack (beta) release due in a few days
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint