You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2004/05/07 00:00:11 UTC

DO NOT REPLY [Bug 28818] New: - XalanEXSLTDateTime not threadsafe, crashing application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28818>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28818

XalanEXSLTDateTime not threadsafe, crashing application

           Summary: XalanEXSLTDateTime not threadsafe, crashing application
           Product: XalanC
           Version: 1.7
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: XalanC
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: Teresa.Selling@mci.com
                CC: Teresa.Selling@mci.com


XalanC 1.8 and XercesC 2.5
Solaris 5.8 and Forte CC 6 update 1

XalanEXSLTFunctionDateTime::execute() uses localtime() and gmtime().  These 
functions are not threadsafe.  It is causing my application to core when 
running multiple threads.  Replacing those two functions with localtime_r() 
and gmtime_r() fixes the problem.  Running under purify, I get Free memory 
read, Freeing unallocated memory, and Free memory write errors in the 
xalanc_1_8::XalanEXSLTFunctionDateTime::execute() method.

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