Hey All,
I just started porting the IDOM interface to Xerces-P and am getting
some wierd behavior, and I wondered if somebody could clue me in.
Just to make sure it wasn't the perl interface I add the following
code to IDOMCount.cpp, and it SIGSEV's as well:
IDOM_DOMImplementation *impl = IDOM_DOMImplementation::getImplementation();
impl->createDocumentType(XMLString::transcode("foo"),
XMLString::transcode("foo"),
XMLString::transcode("foo"));
My test program is segfaulting in IDDocumentImpl::allocate(), and when
I run it in gdb it shows:
#0 0x6fa17e74 in IDDocumentImpl::allocate () at HashXMLCh.cpp:76
#1 0x6fa17cc8 in IDDocumentImpl::cloneString () at HashXMLCh.cpp:76
#2 0x6fa18604 in IDDocumentTypeImpl::IDDocumentTypeImpl () at HashXMLCh.cpp:76
#3 0x6fa1405c in IDDOMImplementation::createDocumentType ()
at HashXMLCh.cpp:76
#4 0x6fc2123c in _wrap_IDOM_DOMImplementation_createDocumentType (
cv=0x1056d604) at Xerces.C:5592
#5 0x10062294 in Perl_pp_entersub ()
#6 0x1005b2c4 in Perl_runops_standard ()
#7 0x10013f60 in S_run_body ()
#8 0x10013c18 in perl_run ()
#9 0x100111d4 in main ()
#10 0x6fd78478 in __libc_start_main () from /lib/libc.so.6
What's the deal with HashXMLCh.cpp? Why does gdb think it's out in the
weeds?
Thanks,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
