Hi Daniel, can you package a small test case that reproduces the error?
Thanks, Alberto
At 11.07 22/11/2004 -0500, White Daniel E CONT DLVA wrote:
It still spews. I even tried adding a call to resetDocumentPool
Still looking for ideas.
How do other folks do it ? Inquiring minds would like to know.
-----Original Message----- From: White Daniel E CONT DLVA [mailto:[EMAIL PROTECTED] Sent: Friday, November 19, 2004 10:52 AM To: '[EMAIL PROTECTED]'; 'Alberto Massari' Subject: RE: Segmentation Fault -- HELP PLEASE !!
Could my problem be in wanting to re-use the parser object ?
How do other folks do this ?
Would I be better off creating a fresh parser for each incoming statement and then deleting it when I have parsed the statement ?
-----Original Message----- From: White Daniel E CONT DLVA [mailto:[EMAIL PROTECTED] Sent: Friday, November 19, 2004 9:06 AM To: '[EMAIL PROTECTED]'; 'Alberto Massari' Subject: RE: Segmentation Fault -- HELP PLEASE !!
As a matter of fact, yes, but each thread has its own instance of the parser. It is created after the thread is activated.
I found something in the Xerces-C FAQ yesterday that makes things a lot more stable, but not yet completely so:
Why does my application crash when deleting the parser after releasing a document? http://xml.apache.org/xerces-c/faq-parse.html#faq-31
So, I added the following lines to my code:
DOMNode *doc = this->parser->getDocument(); this->parser->adoptDocument(); doc->release();
It still crashes/seg-faults , but not nearly as often.
Any ideas about anything else that might need cleaning up ?
-----Original Message----- From: Alberto Massari [mailto:[EMAIL PROTECTED] Sent: Thursday, November 18, 2004 6:00 PM To: [EMAIL PROTECTED] Subject: RE: Segmentation Fault -- HELP PLEASE !! Importance: High
Hi Daniel, by any chance, is the method myStreamHandler::validate run by multiple threads?
Alberto
At 11.45 18/11/2004 -0500, White Daniel E CONT DLVA wrote: >I have reached wits end on this one. > >I am running on RedHat 7.1, with gcc's 2.96-112.7.1 >I even applied the fix-patch from XERCESC-1162 about base class warnings in >SAXException >[..]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
