Bug ID 458949: Error message is not being set on user-supplied variable when using catch command on TCL_ERROR

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0

Opened: Apr 24, 2014

Severity: 4-Minor

Related Article: K52443512

Symptoms

The system receives a Tcl exception on a variable, but does not post an error message.

Impact

Missing error message.

Conditions

This occurs when setting an error message on a user-supplied variable when using the catch command on TCL_ERROR.

Workaround

Use the $::errorInfo indirectly. To do so, use commands similar to the following: -- set static::errorInfo {$::errorInfo}. ... -- log local0. 'error: [subst $static::errorInfo]'.

Fix Information

On TCL_ERROR, there is now an error message set on a user-supplied variable when using the catch command on TCL_ERROR.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips