CoreDumpFile : Program terminated with signal 11, segmentation fault.

[Rohit Khajuria]

Hi All

I recieved an alert CoreDumpFileFound

After analysing the core dump files I found program terminated with signal 11, segmentation fault.

Also find the CUCM Backtrace for your reference 

backtrace - CUCM
===================================
#0 0x02530d30 in strncpy () from /lib/libc.so.6
#1 0x080e1f09 in CQBE_Parser::qbeGet (pMsgBuf_=0xec4eee5c, pParsedMsg_=0xec4fb1ac, pQbeString_=0xec4fb1d4, pNextOffset_=0xec4eee0c) at qbeparser.cpp:433
#2 0x080e38a7 in CTIQBE::ProviderOpenResponse::qbeGet (this=0xec4fb1ac, pMsgBuf_=0xec4eee5c, pNextOffset_=0xec4eee0c) at qbeparser.cpp:2296
#3 0x080ebc84 in CQBE_Parser::qbeParse (this=0xec4ff21e, pInputMsg_=0xec4eee5c, inputMsgLength_=121, pParsedMsg_=0xec4fb1ac, parsedMsgBufferSize_=16384) at qbeparser.cpp:8050
#4 0x080b2b49 in CCtiInterface::receiveLoop (this=0x0) at ctireceiver.cpp:483
#5 0x00000000 in ?? ()

Can Anyone please help me understand this ?

Regards

[Navaneethakrishnan Muralidharan]

It might be related to bug : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtj47847/?reffering_site=dumpcr 

The fixes for other previous CEF related defects were preventive and the intention was to reduce the probability of the crash to happen but they could not eliminate the root cause 100%.

The root cause is a thread synchronization issue in QBEHelper which can still occur in a very rare cases.

Usually it manifests itself during system upgrade where some of the services, mainly DB access, can come up with very noticeable delays