Fun with debugger

[mkossmann]

Today I've got a problem with the debugger in CVI2012 ( 32bit) .  The debugger does always single step mode. I can't jump over a few lines of statements any more within the debugger. Any ideas how fix that ?  

[mkais]

Hi,

Can you upload your Code to try to reproduce the same issue? Did you have tried to debug a sample Example from the CVI Library?

[wally_666]

I don't really get your question.

The CVI debugger works more or less like all the other graphical IDE debuggers out there, although IMHO its the best I've ever seen overall.

Basically set a breakpoint in your code, "debug" the program by running the dbg version of the exe, and once your breakpoint hits you can postion your cursor on the next source line you want to break at and select Run->GoToCursor or press F7 key.

[mkossmann]

The problem was, that the debugger behaved in one function like i would have set a breakpoint for every line of the code ( even after I deleted all breakpoints) and using CTRL-F10 or F7 for jumping over some code did the same as F10 : the debugger stopped executing in the next line of code.

If I remember correctly it started afted I tried to debug a Labwindows/CVI Code Module running in TestStand by setting a Breakpoint at Teststand Level and then attaching CVI ( with the Project for that dll loaded) to the running Seqedit.exe process. Then I used F8 at TestStand level to jump in to the CVI Code.   After that closed Both CVI and   Seqedit.exe. 

When remembering this I started playing again with attaching CVI to Teststands Seqedit.exe and problem seems to be fixed now

[CVI-User]

The debugger also stops when a cvi library error occurs, i.e. a cvi library function is about to return an error.

Have a look at Window >> Threads to check if an other thread caused it.

There are three items in Run >> Break On - play with them.