You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "David Bertoni (JIRA)" <xe...@xml.apache.org> on 2005/05/05 06:03:04 UTC

[jira] Resolved: (XERCESC-1391) Class RangeToken is not thread-safe

     [ http://issues.apache.org/jira/browse/XERCESC-1391?page=all ]
     
David Bertoni resolved XERCESC-1391:
------------------------------------

     Resolution: Fixed
    Fix Version: Nightly build (please specify the date)
                     (was: 2.6.0)

> Class RangeToken is not thread-safe
> -----------------------------------
>
>          Key: XERCESC-1391
>          URL: http://issues.apache.org/jira/browse/XERCESC-1391
>      Project: Xerces-C++
>         Type: Bug
>   Components: Utilities
>     Versions: 2.6.0
>     Reporter: David Bertoni
>     Assignee: David Bertoni
>     Priority: Critical
>      Fix For: Nightly build (please specify the date)
>  Attachments: patch.txt
>
> The class RangeToken initializes its fMap data member the first time on-demand, which makes it sensitive to race-conditions.  I am proposing a patch to the class, with additional patches to the classes that perform static initialization to ensure that when users request full static initialization, the fMap data member of all static RangeToken instances is initialized.
> Although this does not prevent threading problems in all cases, it will fix the problem with all global statics.  I will attempt to propose another patch that takes care of the problem with other uses of RangeToken.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org