Uploaded image for project: 'XalanC'
  1. XalanC
  2. XALANC-511

Crash during XalanTransformer::initialize on AIX

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.9
    • None
    • XalanC
    • None
    • AIX 5.2

    Description

      I am using ICU 3.2, Xerces 2.6 and Xalan 1.9. Aix 5.2.
      Compilers xlC_r for C++ and xlc_r for c. The call
      that caused the crash is
      XalanTransformer::initialize().

      Release build of all components work fine. Debug build
      works fine for xerces and icu. Xalan debug build
      fails with errors in XalanVector.hpp.

      >
      > I am facing two problems while using xalan 1.9. Our
      > application previously used xalan1.4. We now moved
      > to
      > using xalan 1.9. I have downloaded sources for xalan
      > and built it myself (xlc_r, xlC_r version 6). In
      > our
      > initialization code, we make a call to the method
      > XalanTransformer.initialize().
      >
      > Problem 1. After the changes, this call crashes on
      > AIX
      > 5.2. Works finw on hp, linux, solaris and windows.
      > The stack trace shows something thats weird like
      > below. Anybody have any idea
      > <---------------------------->
      > dbx) where
      > .() at 0x0
      > __negpow2() at 0xd6b0ef40
      > __negpow2() at 0xd6b03ac4
      > unnamed block $b3811, line 621 in "arxml.cpp"
      > InitXMLParser(0x2ff22828), line 621 in "arxml.cpp"
      > Initialization(0x1, 0x2ff22918), line 877 in
      > "startup.cpp"
      > main(argc = 1, argv = 0x2ff22918), line 9882 in
      > "arrpcsvc.c"
      > (dbx) q
      > <---------------------------->
      >
      > Problem2: I am trying to build xalan in debug mode
      > to
      > be able to debug through a crash I am seeing on AIX.
      >
      > Release build works fine. But debug build throws
      > this
      > compile error. Is there a known problem with
      > XalanVector.hpp.
      >
      > xlC_r -g -qthreaded -DAIX -D_THREAD_SAFE
      > -I/stlport -DXALAN_INMEM_MSG_LOADER -DXALAN_USE_ICU
      > -c
      > -I/home/essfs1/rmysore/xml-xalan/c/src
      > -I/home/essfs1/rmysore/xml-xalan/c/include
      > -I../../nls/include
      > -I/home/essfs1/rmysore/xerces-c-src_2_6_0/src/
      >
      -I/home/essfs1/rmysore/xerces-c-src_2_6_0/include/xercesc
      > -I/home/essfs1/rmysore/xerces-c-src_2_6_0/include/
      > -I/home/essfs1/rmysore/icu/include -o
      > ../../obj/XalanDOMStringCache.o
      >
      /home/essfs1/rmysore/xml-xalan/c/src/xalanc/PlatformSupport/XalanDOMStringCache.cpp
      >
      "/home/essfs1/rmysore/xml-xalan/c/src/xalanc/Include/XalanVector.hpp",
      > line 405.5: 1540-0704 (S) The definitions of "void
      > xalanc_1_9::XalanVector<xalanc_1_9::XalanDOMString
      > *,struct
      > xalanc_1_9::MemoryManagedConstructionTraits<xala..."
      > and "void
      > xalanc_1_9::XalanVector<xalanc_1_9::XalanDOMString
      > *,struct
      > xalanc_1_9::MemoryManagedConstructionTraits<xala..."
      > have the same linkage signature
      >
      "insert_Q2_10xalanc_1_911XalanVectorXTPQ2_10xalanc_1_914XalanDOMStringTQ2_10xalanc_1 \
      931MemoryManagedConstruction...".
      >

      Attachments

        1. patch.txt
          2 kB
          David N Bertoni

        Issue Links

          Activity

            People

              dbertoni David N Bertoni
              pmysore Prasad Mysore
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: