CVI2013 f1 and breakpoints

[vix]

see attached example:

• build the project
• place a breakpoint at line 56 of callback.c (this line is never executed because SAMPLE_BREAKPOINT is defined as 0)
• run
• the breakpoint moves clicking over it and can't be deleted

[Wolfgang]

This issue probably is related to the one I have reported earlier here - the compiler is optimizing code even in debug version so it knows that the if case is false and hence does not look at this line of code and thus will not realize that there is a breakpoint...

[vix]

Is there a bug ID and/or a CAR for this issue?

Even with f1 patch, I can't really use CVI 2013 for project development, since I has some important regressions compared to CVI 2012 SP1.

Thanks

[Johannes_T · Accepted solution]

Hello vix!

Your guess was correct. There is an existing known issue regarding this problem, which has been introduced in CVI 2013. We are currently dealing with this bug, and a fix should be available soon, in an upcoming release of CVI. The bug report for this issue is described by CAR ID 409933.

Thank you!