08-29-2014 10:50 AM - edited 08-29-2014 10:51 AM
CVI (both 8.5.1 and 2013 SP1) is not respecting my breakpoints if I open the project from a network folder.
It does not "break at first step" also.
I am sure it is in debug mode, and I tried a clean build.
I have all the access rights (read/write/delete/modify/create etc...) on that network folder.
The only solution is to copy the project to a local folder, then it starts to break properly.
I do not think this is expected behavior. Is it?!
08-29-2014 10:52 PM
While compiling (running debug mode) it will create a folder 'cvibuild.(project name)' in the project folder. You delete this folder and run again.
I have seen this is helping similar problems
Sajy
08-30-2014 02:44 AM
09-01-2014 08:55 AM - edited 09-01-2014 08:56 AM
I will appreciate if NI can comment if this is expected behavior.
We are 2 people (see francois_Campbell's thread also) who encountered this issue, and I cannot find a reason why debugging should be disabled when project is on a network folder.
Thanks.
09-02-2014 01:39 PM
Hi ebalci,
I do not believe that this should be expected behavior. I have a few questions for you:
1) What OS are you running CVI on?
2) What happens if you create a simple project from template, add a breakpoint, and then move the project to a network drive?
3) Aside from missing the breakpoint, does the rest of your application execute correctly when placed on the network drive?
Regards,
09-02-2014 02:41 PM
09-03-2014 08:37 AM
Hi ebalci,
Thanks for the update. Just to make sure, I tried it out on my end with a very simple project, and CVI did stop at the breakpoints. Perhaps when you get back from holiday you could give it a try on your machine, and we can work from there!
Regards,
09-04-2014 03:28 AM
I also had this problem a few times. I 'solved' it by closing / reopening CVI. I hadn't noticed whether happened only on network drives, but I do have several projects like this.
05-14-2018 04:30 AM
Closing and reopening CVI solved the problem at my application!
Thanks for the hint
gerygery
02-01-2021 04:39 AM
Thank you! Did the trick for me as well. It is not only confined to network drives. Very frustrating.
In my case it was able to "break on... -> first statement" (using the menu), but the manual breakpoint I put on the very first line did not break.