I have the same kind of error the Parser simply hang and my process stay running without crashing. I attached the gdb debugger on the process and here is the stack trace:
0xc019c1a0 in free+0x130 () from /lib/libc.2 (gdb) where #0 0xc019c1a0 in free+0x130 () from /lib/libc.2 #1 0x2bbdec in refree_Regex_ATTLC+0x20 () #2 0x2ad7d4 in Regex::__dt+0x3c () #3 0xc2437e80 in __niamHelper__FPC15__staticArray_tT1+0x124 () from /lib/libCsup_v2.2 #4 0xc2437f74 in _niam_body+0x88 () from /lib/libCsup_v2.2 #5 0xc2438080 in _niam+0x1c () from /lib/libCsup_v2.2 #6 0xc0185504 in exit+0x74 () from /lib/libc.2 #7 0xc6f959c4 in xehInterpretSavedSigaction+0x2d8 () from /opt/mqm/lib/libmqmcs_r.sl #8 0xc6f95ce4 in xehExceptionHandler+0x2a4 () from /opt/mqm/lib/libmqmcs_r.sl #9 <signal handler called> #10 0xc06647b8 in __unwind_dlmodinfo+0x28 () from /lib/libcl.2 #11 0xc06663ac in U_is_readable+0x78 () from /lib/libcl.2 #12 0xc06661b4 in U_get_shLib_text_addr+0x34 () from /lib/libcl.2 #13 0xc066336c in U_get_previous_frame_x+0x868 () from /lib/libcl.2 #14 0xc243842c in unwind_step+0x54 () from /lib/libCsup_v2.2 #15 0xc2433214 in THPStackWalkState::UnwindOneFrame+0x30 () from /lib/libCsup_v2.2 #16 0xc2434764 in __throw__FPvT1+0xe8 () from /lib/libCsup_v2.2 #17 0xc28b37c0 in AbstractStringValidator::checkContent+0x278 () from /lib/libxerces-c.sl.21 #18 0xc28b34fc in AbstractStringValidator::validate+0x2c () from /lib/libxerces-c.sl.21 #19 0xc296f608 in SchemaValidator::checkContent+0x638 () from /lib/libxerces-c.sl.21 #20 0xc29ca370 in XMLScanner::scanEndTag+0x428 () from /lib/libxerces-c.sl.21 #21 0xc29c9cdc in XMLScanner::scanContent+0x184 () from /lib/libxerces-c.sl.21 #22 0xc29c6fbc in XMLScanner::scanDocument+0xdc () from /lib/libxerces-c.sl.21 #23 0xc28ea5e8 in DOMParser::parse+0x120 () from /lib/libxerces-c.sl.21 #24 0x153b68 in XgwcXmlValidator::validate+0x370 () #25 0x150d18 in XgwcClientToFwfmWorkflowService::sendRequestToFwfm+0x220 () #26 0x12da54 in XgwcXmlGateway::sendRequestToFwfm+0xb4 () #27 0xc3a28 in XmlGwReq+0x3ec () #28 0xe277e794 in _tmsvcdsp+0xc14 () from /vendor/bea/tuxedo8.1/lib/libtux.sl #29 0xe279e1f4 in _tmrunserver+0x19c () from /vendor/bea/tuxedo8.1/lib/libtux.sl #30 0xe277d58c in _tmstartserver+0x194 () from /vendor/bea/tuxedo8.1/lib/libtux.sl >From what I see it seems to try to validate the schema and crash while doing AbstractStringValidator::checkContent. I validated by Schema with XmlSpy and it's both well formed and valid. I'm on unix and something we save the files with CRLF because we edit the files with windows, but I made sure that the file was also Ok on that side. What could be causing this. I'm using an old version of xerces ( ver 2.1.0) and can't upgrade due to project constraint. I'm on HP-UX 11. Thanks Boris Kolpackov-2 wrote: > > Hi Bill, > > Bill Moo <[email protected]> writes: > >> I'm using Xerces in Qt so I've included the code in question: >> >> [...] >> >> Sometimes if I add then remove a character from the XML then save it (the >> XML), it works, other times it just works, but not always, more often >> then >> not it fails. > > I suggest that you try create a small but complete test case that doesn't > depend on Qt and that reproduces the problem. If you can do it, then I can > take a look and debug it. If you can't, then you can try to add code from > your original version, piece by piece, and see what triggers this weird > behavior. > > Boris > > -- > Boris Kolpackov, Code Synthesis > http://codesynthesis.com/~boris/blog > Compiler-based ORM system for C++ > http://codesynthesis.com/products/odb > Open-source XML data binding for C++ > http://codesynthesis.com/products/xsd > XML data binding for embedded systems > http://codesynthesis.com/products/xsde > > -- View this message in context: http://old.nabble.com/Intermittant-parse%28...%29-method-failure-of-SAX2XMLReader-tp32232068p32296241.html Sent from the Xerces - C - Users mailing list archive at Nabble.com.
