LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Debugger hangs.

Hello.

CVI2017 debugger hangs on function H264_DVR_Init() for long time when I run debugging  debug.exe process eats more than 20% cpu time.

The same project under CVI2012 runs debugger normally.

What is the cause?


Project attached.

0 Kudos
Message 1 of 2
(1,950 Views)

Hello z80,

Because the H264_DVR_* functions are performing debug logging, the application takes longer to execute, if the debugger is attached. After some time, the app eventually finishes. However, the program runs smoothly without the debugger attached.

 

Outputing debug output strings is an expensive operation. You could solve this delay if you could remove the debug logging from the library functions that you are using.

 

Best regards,

- Johannes

 

You can see the debug messages printed out in the Debug Output window:

Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
Í˳ö´¦ÀíÏß³Ì
m_pCallback create beginÍ˳ö´¦ÀíÏß³Ì
m_pCallback create endxm_nat_init begin
CNat::Stop beginClose init thread beginsvrip[18.196.29.221] port[8765]xm_nat_init[ip=18.196.29.221],ret:1
pNatStartProc end:m_pCallback=2ca42a0 init succesful
Close init thread beginClose nat deal thread beginClose nat deal thread endxm_nat_exit beginxm_nat_exit endCNat::Stop end

0 Kudos
Message 2 of 2
(1,922 Views)