BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

"If something can go wrong...", or, "have bug, will unravel"

Hi All,
      Having just encountered an annoyingly perverse program "feature", I wondered what odd bugs you-all may remember?
 
Anyway, the following may not even qualify for an odd-bugs thread!  But so it goes...
Was debugging database-logging in auto-test program, without the equipment, and ignoring a bunch of "can't find the hardware" errors.  Was able to generate results for logging.
On quitting, the program would exit, but local DB records weren't getting "Flushed" to remote DB as intended,
so I added a dialog, (inside a T/F case) to see the values being used for logging...
Nothing, no dialog on exit, so I moved the dialog outside the case - it had to execute!
Nothing, no dialog on exit.
 
The rub?
 
...post-quit [missing] hardware clean-up was causing LabVIEW to Quit to DT - right when FP was supposed to close!
 
Regards.
 
 
When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 1 of 2
(3,617 Views)
Is it inside a FOR-loop with an autoindexed input?

If the input is empty, then the loop may not run.

Shane
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 2 of 2
(3,605 Views)