#177 ON ERROR does not work for all errors

[Richard Clarke]

The SCL On Error command is intended to allow script
errors - which would normally cause the thread being
executed to abort - to be captured, and script
execution to be resumed at a predefined label.
Unfortunately, there are some errors that are not
trapped by this command. For example, when the
following errors are reported:

!HTTPRESPONSE: No data available for connection id (n)
!TScript::run: ERROR: TOF execution failed
!Script Execution Failed.

This error was reported on the OpenSTA Users list by
Charlie J. Hewett (charlie.j.hewett@intel.com).

Some errors, such as using an invalid offset within an
~Extract command are trapped correctly, e.g.:

Set myvar = ~Extract (-1, 500, TmpBuf)

OpenSTA Internals Note: The ON ERROR command relies on
command processing code throwing an exception. The
command establishes a label to which a jump will be
made if an exception is caught within the TScript::run
method. If an exception is not thrown up to this
method, the ON ERROR command will not trap the error.

[Charlie Hewett]

Logged In: YES
user_id=210081

I have gotten many different errors and have never gotten
the ON ERROR command to catch the error. Specifically, all
the http related errors are not handled correctly.

e.g. W* Script Error: Error establishing secured
connection on 1/1

[Richard Clarke]

Logged In: YES
user_id=82309

Thanks for your comments Charlie. I suspected that there
may be quite a lot of errors not trapped by the ON ERROR
command. In processing this bug we will, of course, look to
ensure that the ON ERROR command works as documented.