IBM Support

LI76219: DESTRUCTOR CALLED TWICE WITH ?: CONDITIONAL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Using object constructors as the second and third operands in a
    ?: conditional is corrupting the exception unwinding stack.
    
    As an example, a conditional of the form:
    
    object1 = ( true  ?  TestObject(10) : TestObject(11) );
    
    is pushing an extra object reference on to the unwinding stack.
    When an exception is thrown, a destructor is accidentlly called
    twice, possibly resulting in a runtime error or crash.
    

Local fix

  • Change the ?: conditional into an 'if' statement.
    

Problem summary

  • PROBLEM DESCRIPTION:
    Unnecessary exception handling table cloning applied, thus
    creating corrupt exception handling table.
    
    USERS AFFECTED:
    Temporaries constructed within the context of conditional
    expressions may expose the problem when throwing an exception
    after the conditional but before another exception handling
    state change.
    

Problem conclusion

  • The exception handling table cloning has been restricted to
    only the cases where it is needed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI76219

  • Reported component name

    XL C/C++ SLES10

  • Reported component ID

    5724U8300

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-10

  • Closed date

    2011-06-10

  • Last modified date

    2011-06-10

  • APAR is sysrouted FROM one or more of the following:

    IZ92370

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    XL C/C++ SLES10

  • Fixed component ID

    5724U8300

Applicable component levels



Document information

More support for: XL C/C++

Software version: A.1

Reference #: LI76219

Modified date: 10 June 2011