08-28-2014 10:43 AM
Hi,
When debugging my application in CVI 2013, if I set a breakpoint before a call to a function in another C file, the Step Into command just steps over the function call, even though the source for both is my own and both files are included in the project. If I set a breakpoint in the function in the second file, the application doesn't stop at all, preventing me from seeing what is happening.
I have been able to do this in the past and now it is no longer functioning, what could I have possibly changed?
Thanks
Francois Campbell
08-28-2014 11:14 AM
Hello Francois,
If you put the cursor on the function you are calling, right click and select Go to Definition(Ctrl+I) does it take you in the right place? I'm thinking maybe the function that it's called is not the one you expect. I don't see for the moment other reason the debugger doesn't step in.
Constantin
08-28-2014 11:17 AM
Yes, it does take me to the right function, and it executes correctly when run.
08-28-2014 01:57 PM
It maybe jumping to the right fucntion, but does it jump to the right file?
Do you have multiple copies of that file, old and new versions maybe?
If so, the project might have been messed up with incorrect versions.
Can you check the function it jumps is the correct file?
08-29-2014 05:42 AM
If you call Breakpoint() inside the function you are calling, does the debugger stop?
08-29-2014 07:06 AM
Hi Everyone,
It seems that coming back this morning and starting fresh, the issue is resolved. I don't know what did it, but everything is working fine. Thanks for your help.
08-29-2014 10:41 AM
This happens some time with CVI.
When I start to get strange responses out of nowhere, I always do a system restart first 😉
08-29-2014 10:45 AM - edited 08-29-2014 10:52 AM
I also very recently encountered such a situation.
I don't know why I couldn't remember it before.
CVI was not respecting my breakpoints at all.
It did not even do "break at first step".
Then it turned out that, it was becasue the files were on a network drive, not stored locally in my hard disk.
This also surprised me, because I had all the access rights on that network folder.
The only solution was to copy the project to a local folder, then it started to break appropriately.
I do not think this is expected behavior.
Maybe I should create e new thread for this issue of mine.
All the best,
08-31-2014 10:27 AM
08-31-2014 11:42 AM