Hi David, Thanks for your reply. It helped me to track down the real cause of the issue. Although both "initialize" methods were being called correctly, it turns out that the class they were being called from had a private member variable of type XalanTransformer, so it's default construct was being called before both methods, resulting in the error. Thanks again!
On 4/6/10 5:37 PM, "David Bertoni" <dbert...@apache.org> wrote: > On 4/6/2010 8:11 AM, Garett Chang wrote: >> Hi, >> >> I¹m porting some programs I¹ve inherited from Tru64 to HP-UX (IA64). The >> code uses Xalan 1.10, along with Xerces 2.7. I¹m running into an issue >> where the program core dumps when calling >> XalanTransformer::initialize(). Below is an output from a gdb session. >> If it¹s worth mentioning, we¹re using a third party product that already >> comes with the Xalan and Xerces libraries precompiled. >> >> #0 0xc00000002336d7c0:0 in >> xalanc_1_10::XalanVector<char,xalanc_1_10::MemoryManagedConstructionTraits<ch >> ar> >>> ::allocate () >> >> at /users/cesc2/3rdparty/xml-xalan/c/src/xalanc/Include/XalanVector.hpp:944 >> >> #1 0xc000000023370e60:0 in >> xalanc_1_10::XalanVector<char,xalanc_1_10::MemoryManagedConstructionTraits<ch >> ar> >>> ::ensureCapacity () >> >> at /users/cesc2/3rdparty/xml-xalan/c/src/xalanc/Include/XalanVector.hpp:169 >> >> #2 0xc0000000233c4840:0 in >> xalanc_1_10::XalanVector<char,xalanc_1_10::MemoryManagedConstructionTraits<ch >> ar> >>> ::insert () >> >> at /users/cesc2/3rdparty/xml-xalan/c/src/xalanc/Include/XalanVector.hpp:427 >> >> #3 0xc000000023c21580:0 in >> xalanc_1_10::XalanTransformer::XalanTransformer () >> >> at /users/cesc2/3rdparty/xml-xalan/c/src/xalanc/Include/XalanVector.hpp:907 >> >> #4 0xc000000023c222b0:0 in >> xalanc_1_10::XalanTransformer::XalanTransformer () > This call stack does not indicate you've called > XalanTransformer::initialize(). It indicates you've called the > constructor for XalanTransformer. Are you sure you've provided the right > call stack? I would expect to see this crash if you haven't called > PlatformUtils::Initialize() or XalanTransformer::initialize(), because > the default MemoryManager instance would be NULL. > > Also, if you could provide more details about what caused the core dump, > that would help. Is it a segmentation fault, or something else? > > Dave
