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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25662

fgMemoryManager varible being re-initialized

           Summary: fgMemoryManager varible being re-initialized
           Product: XalanC
           Version: 1.6
          Platform: Other
        OS/Version: AIX
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: XalanC
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I compiled xerces 2.3 and Xalan 1.6 on AIX 5.2 using g++ 3.3.1

When I run my application with libxerces-c23.0.so and libxalan-c16.so I find 
that the variable fgMemoryManager get re-initialized to null.

Here is a diagram of what is happening in my code.

My main program calls 
void XMLPlatformUtils::Initialize(const char*          const locale
                                , const char*          const nlsHome
                                ,       PanicHandler*  const panicHandler
                                ,       MemoryManager* const memoryManager)

which establishes an address for fgMemoryManager=214739d8 I return out of this 
function back to my main where I test the value of fgMemoryManager and it is 
still set to the same address.

main: fgMemoryManager=214739d8

My main program makes the following call:
stylesheet = processor.processStylesheet(xslFileName, theConstructionContext);

Inside XSLTEngineImpl.cpp
StylesheetRoot*
XSLTEngineImpl::processStylesheet(
            const XalanDOMString&           xsldocURLString,
            StylesheetConstructionContext&  constructionContext)

I print the value of fgMemoryManager and it is now NULL. I can't figure out why 
this is being re-initialized.

To make things more compilcated when I statically link all the xerces/xalan 
*.o's into my main program (remove the shared objects) this variable stays 
initialized and my program appears to work.

Any input regarding this issue would be very much appreciated. If you would 
like to email me directly I can be reached at

[EMAIL PROTECTED]

Reply via email to