Do you have a fix for the break point BUG in CVI 7.0?

[SRB]

Why does CVI 7.0 prevent me from setting break points at certain places? Often I get the following error when trying to run the debug: "Cannot set breakpoint. Line *** has no executable code."

I can put in i = 1; and try to set a break point but get the same error. The error is does not always occur, but it is very annoying as I cannot always set breakpoints where I need.

Anything know about or how to fix this error would be greatly appriciated.

[RobertoBozzolo]

I am presently working with CVI 6 and noticed the same strange behaviour.

Seems as if the IDE doesn't take trace of the editings made in the source code, since this happens often when some limes of code are added or deleted and usually it disappears saving the file (in the worst cases I have to put away the breakpoint, recompile the file and set up the breakpoit again).

[JuanCarlos]

As you know CVI will not let you set a breakpoint in a line of code where there is no actual machine code to be executed. CVI will prompt you if you want to move the breakpoint to the next executable line.

I think the problem that you are seeing has to do with the line assignment, CVI marks the line as a non executable line, then some edits happen in the editor but now the line numbers do not correspond.

Something like this happens when you compile a file, get some errors and start fixing them. If the edits change the lines then when you double click on an error takes you to the wrong line.

To avoid this just try to save and compile your files prior to start debugging, I'll also sent this comments to our developers to improve this behavior.

Regards,


Juan Carlos
N.I.

[DaveC]

So has there been any improvement on this bug other than what JuanCarlos gave as a workaround (this workaround doesn't even seem to work a lot of the times.).

Lately I have been having quite a bit of trouble with this bug and it's rather annoying, especially when the only lines I can move the breakpoint to are blank lines that just get skipped over during the debugging phase.  Perhaps a patch has come out to fix this as I couldn't find anything else posted about it in the last couple years?

[LuisG]

Dave,

This bug is being fixed in CVI 8.0, which is currently in beta. There was no patch for this problem.

Luis
NI