[ http://nagoya.apache.org/jira/browse/XERCESC-1289?page=comments#action_55288 ] Alberto Massari commented on XERCESC-1289: ------------------------------------------
Would it be possible for you to post the code of the function SocksClient::parseXMLResponse? It's hard to understand what is going on from just the stack trace. Thanks, Alberto > Xerces-c++ version 2.60 crashes. > -------------------------------- > > Key: XERCESC-1289 > URL: http://nagoya.apache.org/jira/browse/XERCESC-1289 > Project: Xerces-C++ > Type: Bug > Components: DOM > Versions: 2.6.0 > Environment: Solaris 9. > Reporter: Mukund Sundararajan > > I'm using xerces-c++ version 2.6.0 in my multi-threaded client-server > application on solaris 9. I got the binaries for xerces-c from > xml.apache.org. Upon running a load test on my application, it crashed with > the following stack trace from dbx - > =>[1] > xercesc_2_6::NameIdPool<xercesc_2_6::DTDElementDecl>::removeAll(0x21efe8, > 0x2487f0, 0xfeaf2248, 0xfeaf2248, 0xfec4eb88, 0x0), at 0xfea15b88 > [2] > xercesc_2_6::NameIdPool<xercesc_2_6::DTDElementDecl>::~NameIdPool(0x21efe8, > 0x21eea0, 0xfecb30cc, 0xfeaf2248, 0x0, 0x21eea8), at 0xfea15b18 > [3] xercesc_2_6::IGXMLScanner::cleanUp(0x2b7818, 0xfeb1bd40, 0xfec6a998, > 0xfead4244, 0xfec5e030, 0xfea172c4), at 0xfeae0bc4 > [4] xercesc_2_6::IGXMLScanner::~IGXMLScanner(0x2b7818, 0x2f00, 0xf4b74, > 0x6d058, 0xfec4eb88, 0x6cf98), at 0xfeadfb48 > [5] __SLIP.DELETER__P(0x2b7818, 0x1, 0xfeae6790, 0x246ad0, 0x0, 0x1af400), > at 0xfeae6794 > [6] xercesc_2_6::AbstractDOMParser::cleanUp(0xf947bba4, 0xfec61034, 0x0, > 0xfec61088, 0xfec610ac, 0xfec610f8), at 0xfea6cf1c > [7] xercesc_2_6::AbstractDOMParser::~AbstractDOMParser(0xf947bba4, 0xf6a70, > 0x246ad4, 0xf947bb98, 0x0, 0x6), at 0xfea6ccac > [8] SocksClient::parseXMLResponse(0xf6a70, 0xf947bf28, 0x244310, 0x189, > 0x2c00, 0x2db4), at 0x49914 > My application uses the DOMWriter to generate xml documents and DOM parser to > parse them. The application does both generation and parsing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
