Core in resetDocumentPool API in XercesDOMParser

["Priya Mollyn (pmollyn)" <pm...@cisco.com>]

Hi,
 
We have a core generated while calling resetDocumentPool() in the
XercesDOMParser, below is the back trace. parser object is used by only
one thread, processing documents sequentially. parser is initialized
correctly. Any idea why this crash ? Has anyone seen this before ?
 
 
#0  0x087bd61f in ?? ()
 
(gdb) bt
 
#0  0x087bd61f in ?? ()
#1  0x0000002b in ?? ()
#2  0x0095b395 in xercesc_2_6::DOMDocumentImpl::~DOMDocumentImpl$delete
()
   from /usr/local/cm/lib/libxerces-c.so.26
#3  0x0095e150 in xercesc_2_6::DOMDocumentImpl::release ()
   from /usr/local/cm/lib/libxerces-c.so.26
#4  0x00925a00 in xercesc_2_6::AbstractDOMParser::resetPool ()
   from /usr/local/cm/lib/libxerces-c.so.26
#5  0x00a1961b in xercesc_2_6::XercesDOMParser::resetDocumentPool ()
   from /usr/local/cm/lib/libxerces-c.so.26
#6  0x080f9238 in CSnmpAlarmReceiver::parseRawAlarm (curRawAlarm=
      {<_STL::_String_base<char, _STL::allocator<char> >> = {_M_start =
0x87c6508 "<Alarm Name=\"CALLMGMT-CISCOCALLMANAGER-DeviceRegistered\"
Sev=\"6\" Time=\"1155686670\"><Param Name=\"DeviceName\" Type=\"String\"
Value=\"SEPCA21CC210005\"></Param><Param Name=\"IPAddress\"
Type=\"String\" Value=\"1"..., _M_finish = 0x87c6828 "",
_M_end_of_storage = {<_STL::allocator<char>> = {<No data fields>},
_M_data = 0x87c6829 "\003"}}, static npos = 4294967295},
parsedAlarm=@0xd7f69b0)
    at SnmpAlarmReceiver.cpp:260
#7  0x080f9e7e in CSnmpAlarmReceiver::workerThread
(pAlarmReceiver=0xb702bee0)
    at SnmpAlarmReceiver.cpp:452
#8  0x003df2e6 in ACE_Thread_Adapter::invoke_i (this=0xb709b410)
    at Thread_Adapter.cpp:150
#9  0x003df251 in ACE_Thread_Adapter::invoke (this=0xb705bf20)
    at Thread_Adapter.cpp:93
#10 0x003a645e in ace_thread_adapter (args=0xb7027b70)
    at Base_Thread_Adapter.cpp:121
#11 0x00129dec in start_thread () from /lib/tls/libpthread.so.0
#12 0x00581a2a in clone () from /lib/tls/libc.so.6
 
Thanks
-Priya 
 

Re: Core in resetDocumentPool API in XercesDOMParser

[David Bertoni <db...@apache.org>]

Priya Mollyn (pmollyn) wrote:
> Hi,
>  
> We have a core generated while calling resetDocumentPool() in the 
> XercesDOMParser, below is the back trace. parser object is used by only 
> one thread, processing documents sequentially. parser is initialized 
> correctly. Any idea why this crash ? Has anyone seen this before ?
>  

Did you delete the DOMDocument instance yourself?  If so, did you call 
AbstractDOMParser::adoptDocument() before you did that?  If not, the parser 
instance will attempt to delete the document.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org