Ticket #229 (closed defect: fixed)

Opened 3 months ago

Last modified 3 months ago

order-of-initialization-of-globals issue

Reported by: jasper Owned by: jasper
Priority: blocker Milestone: Phase III WP1
Component: Client Header Files Version: 1.2.0.14
Keywords: Cc:

Description

All vTable objects of data types are static globals.

COBIA initialize is called from a static initializer in some applications (including cobiaRegister) as well.

COBIA initialization checks for version, which uses CapeStringImpl?.

The CapeStringImpl? is not necessarily initialized at this point.

Change History

comment:1 Changed 3 months ago by jasper

  • Priority changed from major to blocker

comment:2 Changed 3 months ago by jasper

This is marked as a blocker - we should not release with this issue.

comment:3 Changed 3 months ago by jasper

We have a facility for this: create all vTables from a static function, which ensures proper initialization. Switching to this machinary permanently to resolve the issue.

comment:4 Changed 3 months ago by jasper

  • Status changed from new to closed
  • Resolution set to fixed

In [b293ec0aec003ab603f22b1df2afd49aca758e3d]:

fixed #229

comment:5 Changed 3 months ago by jasper

Correction: cobiaRegister does not initialize COBIA in a static initializer. But some dependent application do and potentially (as observed) crash on this issue.

Note: See TracTickets for help on using tickets.