Albert Chin wrote:
I built Xerces C 2.7.0 and Xalan C 1.10.0 as follows: $ gtar zxf xerces-c-src_2_7_0.tar.gz $ cd xerces-c-src_2_7_0/src/xercesc $ XERCESCROOT=/opt/build/china/xerces-c-src_2_7_0 \ ./runConfigure -c cc -x cxx -b 32 -p tru64 -d $ XERCESCROOT=/opt/build/china/xerces-c-src_2_7_0 gmake
...
$ cd cd /opt/build/china/xml-xalan/c/src/xalanc/Utils $ ladebug ../../../bin/MsgCreator core (ladebug) where >0 0x3ff805bac48 in __nxm_thread_kill(...) in /usr/shlib/libpthread.so #1 0x3ff805b4224 in pthread_kill(...) in /usr/shlib/libpthread.so #2 0x3ff805bea6c in UnknownProcedure3FromFile99(...) in /usr/shlib/libpthread.so #3 0x3ff807f369c in UnknownProcedure15FromFile0(...) in /usr/shlib/libexc.so #4 0x3ff807f3a08 in exc_raise_signal_exception(...) in /usr/shlib/libexc.so #5 0x3ff805b5b7c in UnknownProcedure283FromFile0(...) in /usr/shlib/libpthread.so #6 0x3ff800d14ec in __sigtramp(...) in /usr/shlib/libc.so #7 0x3ffbffcc8fc in __nw__7XMemoryXUl(size=16) "XMemory.cpp":37 #8 0x3ffbfefe4f8 in XMLPlatformUtils::Initialize(locale=0x3ffbfd2af38="en_US", nlsHome=0x0, panicHandler=0x0, memoryManager=0x0, toInitStatics='\000') "PlatformUtils.cpp":276 #9 0x120035dd0 in main(argC=6, argV=0x11fffc018) "/opt/build/china/xml-xalan/c/src/xalanc/Utils/MsgCreator/MsgCreator.cpp":288 #10 0x1200332a8 in __start(...) in ../../../bin/MsgCreator
The call stack indicates it's coming from Xerces-C's XMLPlatformUtils::Initialize() so I suspect it's a problem with Xerces-C. Have you tried running any of the tests or samples for Xerces-C? Note that we no longer have access to a working Tru64 machine, so the Xerces-C and Xalan-C ports for Tru64 are out-of-date.
Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
