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 2003/01/01 11:02:44 UTC

DO NOT REPLY [Bug 15749] New: - s_spaceAttrQName not being initialised properly under linux

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=15749>.
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=15749

s_spaceAttrQName not being initialised properly under linux

           Summary: s_spaceAttrQName not being initialised properly under
                    linux
           Product: XalanC
           Version: 1.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: XalanC
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: berin@ozemail.com.au


I have been getting assert problems to do with QNames being NULL when they 
shouldn't be - but only on a Debian 3.0 box.  (gcc 2.95.4)

Attached a debugger and found that for some reason s_spaceAttrQName is a 
reference to two 0x0 strings.

Given this is a QNameByReference I _think_ it might be something to do with 
order of initialisation of globals - s_spaceAttrQName being initialised during 
start up prior to DOMServices::s_XMLNamespaceURI etc.

I found that if I move the static to a normal (non-static) variable and 
initialise in the constructor everything works fine.

There are no problems at all on my Windows box, just the Linux.  (Have not yet 
tried on Solaris.)

Will attach patches in case they are of use.