Hi ,
I had been looking for a crash on my Mac OS X while calling
XalanTransformer::Initialize().
I guess my test application is not able to get definition of
"initGuard" and "inputSourceGourd", called from
XalanTransformer::Initialize(). Where I can get these definitions ? This may
resolve the issue.
ThanX
Pranav Kumar Sahu
-----Original Message-----
From: Peter Guyatt [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 27, 2003 2:05 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem in using Xalan1.6 with Mac OS X
Hi There,
Just try 1.4 and if you dont get any error then stay with that until
Xercers2.4 and Xalan1.7
Thanks
Pete
-----Original Message-----
From: Pranav Kumar Sahu [mailto:[EMAIL PROTECTED]
Sent: 27 November 2003 04:25
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Problem in using Xalan1.6 with Mac OS X
HI,
Yes my application does not build with Xerces2.3. I have not tried to
resolve as i am looking for Xerces2.4 to be released.
So with existing stuff i am bound with Xerces2.1. Do you think i have to use
Xalan1.4 with my Xerces2.1.
Is there no way out.
--Pranav
-----Original Message-----
From: Peter Guyatt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 8:12 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem in using Xalan1.6 with Mac OS X
Hi There,
I used Xalan1.5 with Xerces2.3.0 and got all kinds of problems with
it
randomly crashing during transformations which was not always guarnteed.
Moving to Xerces2.2.0 solved this for me.
Upgrading to Xerces2.3.0 should be painless or is it that you can not
recompile your app.
Thanks
Pete
-----Original Message-----
From: Pranav Kumar Sahu [mailto:[EMAIL PROTECTED]
Sent: 26 November 2003 13:58
To: [EMAIL PROTECTED]
Subject: RE: Problem in using Xalan1.6 with Mac OS X
Hi Pete,
I have my application that already uses Xerces2.1. So i can't move
to 2.3 as off now. That's why before building Xalan1.6, I did asked about
compatible issue. And I got a mail from david_n_bertoni that I can use
Xerces2.1 with Xalan1.6. That's why I moved forward on building xalan1.6.
Otherwise I could have been using lower version on xalan may be Xalan1.4 or
so.
ThanX
--Pranav
-----Original Message-----
From: Peter Guyatt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 7:32 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem in using Xalan1.6 with Mac OS X
Hi There
User Xerces 2.3.0
Thanks
Pete
-----Original Message-----
From: Pranav Kumar Sahu [mailto:[EMAIL PROTECTED]
Sent: 26 November 2003 13:46
To: [EMAIL PROTECTED]
Subject: Problem in using Xalan1.6 with Mac OS X
Hi,
I am able to build Xalan1.6 with CodeWarrior8.3. I have used
following code in my test application to just
initialize Xalan.
#include <Carbon/Carbon.h>
#include <xalanc/Include/PlatformDefinitions.hpp>
#if defined(XALAN_CLASSIC_IOSTREAMS)
#include <iostream.h>
#else
#include <iostream>
#endif
#include <xercesc/util/PlatformUtils.hpp>
#include <xalanc/XalanTransformer/XalanTransformer.hpp>
int main(void)
{
XALAN_USING_XERCES(XMLPlatformUtils)
XALAN_USING_XALAN(XalanTransformer)
// Call the static initializer for Xerces.
XMLPlatformUtils::Initialize();
// Initialize Xalan.
XalanTransformer::initialize();
// Terminate Xalan...
XalanTransformer::terminate();
// Terminate Xerces...
XMLPlatformUtils::Terminate();
return 0;
}
Note that i am using Xerces2.1 framework with Xalan1.6.
This code crashes at XalanTransformer::initialize()
Here is crash stack that i got from My Mac :
****************************************************************************
*****************
Thread 3 Crashed:
#0 0x90004b28 in szone_malloc
#1 0x900049a4 in malloc_zone_malloc
#2 0x034db5c4 in operator new(unsigned long)
#3 0x03408224 in std::allocator<unsigned short>::allocate(unsigned long,
void const*)
#4 0x03417f20 in std::__vector_pod<unsigned short, std::allocator<unsigned
short> >::reserve(unsigned long)
#5 0x03417aa4 in std::__vector_imp<unsigned short, std::allocator<unsigned
short>, (bool)1>::reserve(unsigned long)
#6 0x03417a84 in std::vector<unsigned short, std::allocator<unsigned
short> >::reserve(unsigned long)
#7 0x0334b874 in xalanc_1_6::doTranscodeFromLocalCodePage(char const*,
unsigned long, bool, std::vector<unsigned short, std::allocator<unsigned
short> >&, bool)
#8 0x0334b914 in xalanc_1_6::TranscodeFromLocalCodePage(char const*,
unsigned long, std::vector<unsigned short, std::allocator<unsigned short>
>&, bool)
#9 0x0334a844 in xalanc_1_6::doTranscode(char const*, unsigned long,
std::vector<unsigned short, std::allocator<unsigned short> >&, bool)
#10 0x0334a704 in xalanc_1_6::XalanDOMString::append(char const*, unsigned
long)
#11 0x03349fdc in
xalanc_1_6::XalanDOMString::XalanDOMString[in-charge](char const*, unsigned
long)
#12 0x03405610 in xalanc_1_6::TranscodeFromLocalCodePage(char const*,
unsigned long)
#13 0x0333956c in xalanc_1_6::DOMServices::initialize()
#14 0x0333821c in xalanc_1_6::DOMSupportInit::initialize()
#15 0x03338174 in xalanc_1_6::DOMSupportInit::DOMSupportInit[in-charge]()
#16 0x033bec84 in xalanc_1_6::XSLTInit::XSLTInit[in-charge]()
#17 0x0335d5d4 in xalanc_1_6::XalanTransformer::initialize()
****************************************************************************
********************************
And i am getting an error message
"Operating system error -39
Logical end-of-file reached during read operation"
I feel it is looking for some other ".dylb". Does it sound good, if
so what ?
Any clues or suggestions are welcome.
ThanX
Pranav Kumar Sahu
