You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Prasad Mysore (JIRA)" <xa...@xml.apache.org> on 2005/05/07 04:44:09 UTC

[jira] Created: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Crash during XalanTransformer::initialize on AIX
------------------------------------------------

         Key: XALANC-511
         URL: http://issues.apache.org/jira/browse/XALANC-511
     Project: XalanC
        Type: Bug
  Components: XalanC  
    Versions: 1.9    
 Environment: AIX 5.2 
    Reporter: Prasad Mysore


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...".
> 


-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "David Bertoni (JIRA)" <xa...@xml.apache.org>.
    [ http://issues.apache.org/jira/browse/XALANC-511?page=comments#action_12329888 ] 

David Bertoni commented on XALANC-511:
--------------------------------------

Any platform that supports IEEE 754, which we require, will have quiet NaN, so the check is not necessary.  I will look for a spot to add a general compile-time assert just in case.

> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore
>     Assignee: David Bertoni
>  Attachments: patch.txt
>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "Dmitry Hayes (JIRA)" <xa...@xml.apache.org>.
    [ http://issues.apache.org/jira/browse/XALANC-511?page=comments#action_12319083 ] 

Dmitry Hayes commented on XALANC-511:
-------------------------------------

Hi Dave ! Are you planning to commit the fix ? Thanks!


> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore

>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Assigned: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "David Bertoni (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANC-511?page=all ]

David Bertoni reassigned XALANC-511:
------------------------------------

    Assign To: David Bertoni

> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore
>     Assignee: David Bertoni
>  Attachments: patch.txt
>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "Prasad Mysore (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANC-511?page=comments#action_64681 ]
     
Prasad Mysore commented on XALANC-511:
--------------------------------------

Dave gave me a patch that fixes this problem.  Here is the snippet from mail exchange. The problem was with the sqrt(-2.01) call in DoubleSupport.cpp

Thanks Dave.

This seems to work.  I will open a jeera report on
this issue. 

Prasad

--- david_n_bertoni@us.ibm.com wrote:
> > If it is a workaround you cant include in the code
> > because of portability and maintenance reasons, is
> > there something I can do at my end.  May be
> include
> > the workaround code change only for my AIX build
> etc. 
> > If so, can you let me know what the workaround is.
>  We
> > do this initialization during our server startup
> and 
> > so this crash pretty much has rendered the server
> > useless. The workaround will buy me time to
> > investigate if we are doing something wrong in our
> > linking/compiling.
> 
> You can try the following patch, which seems to work
> on my AIX machine.
> 
> Index: DoubleSupport.cpp
>
===================================================================
> RCS file: 
>
/home/cvspublic/xml-xalan/c/src/xalanc/PlatformSupport/DoubleSupport.cpp,v
> retrieving revision 1.7
> diff -r1.7 DoubleSupport.cpp
> 19a20,22
> > #if defined(_AIX)
> > #include <cfloat>
> > #endif
> 33c36,38
> < 
> ---
> > #if defined(_AIX)
> > DoubleSupport::NumberUnion         
> DoubleSupport::s_NaN = { DBL_QNAN };
> > #else
> 34a40
> > #endif
> 48a55
> > #if !defined(_AIX)
> 57a65
> > #endif
> 
> Also, please open a Jira report, so we can track
> this.  We may need to 
> re-work this code so we don't call sqrt() any
> longer.  You can open an 
> issue here:
> 
> http://issues.apache.org/jira/browse/XALANC
> 
> Dave
> 


> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore

>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Resolved: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "David Bertoni (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANC-511?page=all ]
     
David Bertoni resolved XALANC-511:
----------------------------------

    Resolution: Fixed

Patch applied.

> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore
>     Assignee: David Bertoni
>  Attachments: patch.txt
>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "Dmitry Hayes (JIRA)" <xa...@xml.apache.org>.
    [ http://issues.apache.org/jira/browse/XALANC-511?page=comments#action_12329860 ] 

Dmitry Hayes commented on XALANC-511:
-------------------------------------

We can take a little bit safer approach and check first with "numeric_limits<doable>::has_quiet_NaN" , and if not , fallback to the old approach ? Thanks!


> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore
>     Assignee: David Bertoni
>  Attachments: patch.txt
>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-511) Crash during XalanTransformer::initialize on AIX

Posted by "Dmitry Hayes (JIRA)" <xa...@xml.apache.org>.
    [ http://issues.apache.org/jira/browse/XALANC-511?page=comments#action_12331503 ] 

Dmitry Hayes commented on XALANC-511:
-------------------------------------

Let's commit the patch , thanks!

> Crash during XalanTransformer::initialize on AIX
> ------------------------------------------------
>
>          Key: XALANC-511
>          URL: http://issues.apache.org/jira/browse/XALANC-511
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: 1.9
>  Environment: AIX 5.2 
>     Reporter: Prasad Mysore
>     Assignee: David Bertoni
>  Attachments: patch.txt
>
> 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...".
> > 

-- 
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org