Roll up, roll up for the mystery error

[Daklu]

Had this little beaut pop up while stepping through a BD a few minutes ago. Locked up LV hard. Hadn't seen it before and since I have a few minutes while LV acks my three-finger salute I figured I'd share.


The magical mystery error is blowing my BD away
Blowing my BD away, BD away

[crelf]

QUOTE (Daklu @ Mar 3 2009, 04:06 PM)

http://lavag.org/old_files/monthly_03_2009/post-7603-1236114009.png' target="_blank">

Did you have a probe on an error cluster?

We've got everything you need - satisfaction gaurenteed.

[Daklu]

QUOTE (crelf @ Mar 3 2009, 01:31 PM)

Did you have a probe on an error cluster?

Well not anymore... :laugh: I could have at the time though. Why?

Koo koo kachoo

[crelf]

QUOTE (Daklu @ Mar 3 2009, 04:55 PM)

Well not anymore... :laugh: I could have at the time though. Why?

It's the "[4] error out" that's the key - that was the window title of your fourth probe, and it was probing an error wire. I'd say that there was something that crapped itself in there that required LabVIEw to reset it.

[Darren]

Looking at the diagram of the Conditional Error Probe (vi.lib\_probes\default\ConditionalErrorProbe.vi), it looks like either the General Error Handler CORE.vi or that mysterious Conditional Disable Structure is to blame.

-D

[hooovahh]

So what handles the error from the "General Error Handler CORE.vi"? Does it recursively handle errors generated by itself?

We have odd situation where an engine performs a cleanup before exiting, but if an error is generated during the cleanup it will handle the error by prompting the user then exiting. Of course if it tries to exit it will perform the cleanup, but if an error is generated during the cleanup it will handle the error by prompting the user then exiting. This cycle could go on forever.

We have to be mindful of what kind of errors we might see, and what ones we want to retry on, and what ones we want to just exit on, and disregard the cleanup.