Unix system crashing - Need help to identify the issue

Hi,
We are accessing our remote webserver using libcurl.We are using GET method to post the request.The request is a simplified URL.We will receive XML Response for the URL request.
Problem
For Few Scenarios, response for the URL request is received & our component is killed abruptly. Can anyone pls help me what would be the reason for this issue at the earliest.
I have attached the core dump below which will help to track the issue clearly.


core dump: :

fe2d65e0 _malloc_unlocked (800, 0, 6582f8, fe2d63a0, 6ed718, 0) + 230
fe2d6394 malloc (800, 1, e8070, fec574e0, fe3be3c0, fe3c85b8) + 4c
fec574e0 __1c2n6FI_pv_ (800, 1c, e8070, 15540, fec6c9f8, fe3c85b8) + 2c
fe625868 __1cLxercesc_2_5RMemoryManagerImplIallocate6MI_pv_ (65018, 800, 20, b3bf08, 1, b3bf08) + 14
fe6990fc __1cLxercesc_2_5MXMLBufferMgrLbidOnBuffer6M_rn0AJXMLBuffer__ (d63dbc, fe7f0f9a, 37, 8004, 4, 37) + e4
fe6ab880 __1cLxercesc_2_5KXMLScannerLscanXMLDecl6Mkn0BJDeclTypes__v_ (d63ce8, 1, d63dbc, ea610, 0, d63d58) + 18
fe6ab658 __1cLxercesc_2_5KXMLScannerKscanProlog6M_v_ (d63ce8, 6ef458, 1, 7, 1, 1a273f8) + c8
fe611d84 __1cLxercesc_2_5MIGXMLScannerMscanDocument6Mrkn0ALInputSource__v_ (d63ce8, 0, fe611d3c, 0, 18c, fee726fc
) + 48
fe594c04 __1cLxercesc_2_5RAbstractDOMParserFparse6Mrkn0ALInputSource__v_ (19e758, fb1fb080, 4f9, 26f308, d63ce8,
65018) + 8c
fee20bb8 __1cKXMLWrapperQXMLWrapperCommon6MpnHLogging_pnMHttpResponse__v_ (19e750, 2fc, fe7c8e98, fee430b8, 0, 26
f308) + 12c
fee20a34 __1cKXMLWrapper2t5B6MpnHLogging_pnMHttpResponse_nUt_requestSensitivity__v_ (19e750, e1d38, b46b08, 0, fe
c6c9f8, 19e750) + 94
ff244da4 __1cJCMPClientKscrRequest6MrnJRWCString_pkcpc_i_ (e36c8, fb1fb404, fb1fb414, fb1fb860, ff257664, ff2470f
d) + 1d0
ff2439fc __1cJCMPClientOserviceRequest6MpknMASOF_Message_r3_i_ (e36c8, 44c, fb1fbf3c, 0, fb1fb860, fb1fb40c) + 18
4
feebb584 __1cRASOF_WorkDirectorLcallService6MpknMASOF_Message_r3_i_ (5a998, 2461e8, fb1fbf3c, ff258030, 2461ec, f
f243878) + 1a8
feebbd88 __1cRASOF_WorkerThreadNthreadRoutine6M_v_ (5d338, feed07f0, feed0758, 0, fe027200, 1) + 80
feebbe8c workerThreadRoutine (5d338, fb1fc000, 0, 0, feebbe88, 0) + 4
fe346d4c _lwp_start (0, 0, 0, 0, 0, 0)

Last edited on
Well malloc doesn't like something on its stack. Are you saying that your UNIX kernal dumps core, or a process?

Without more data, I would guess that something in the XML is funky. Try to log what you're receiving (write it to a log file perhaps.) I always find truss very helpful. Depending on what flavor of UNIX you have, the truss program may be called something different.

Good luck!
Thanks Kooth...
Our process ( asof _ace ) dumps the core. And we tried to simulate the same scenario with the exact XML response which was returned while crashing, but the system didn’t crash, every thing was fine.

XML resonse

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <searchCustomerResponse xmlns="http://capabilities.nat.bt.com/xsd/crm/v3/Customers">
- <listOfSearchResults>
- <searchResult>
<customerAccountId>xxxxx</customerAccountId>
<name>Mr BROOKE HALLIWELL</name>
<creditScore />
<type>CONSUMER</type>
<primaryContactId>xxxxx</primaryContactId>
<billingAccountNumber>xxxxxx</billingAccountNumber>
<billingAccountStatus>Closed</billingAccountStatus>
<telNo>xxxxxxx</telNo>
<restrictedVisibilityIndicator>Y</restrictedVisibilityIndicator>
- <address>
<id>xxxx</id>
<shortDescription>16, , , TIBBERSLEY AVENUE, BILLINGHAM, TS23 1JP</shortDescription>
</address>
<accountManager />
</searchResult>
- <searchResult>
<customerAccountId>xxxxxx</customerAccountId>
<name>BTSS (CORAL RACING)</name>
<creditScore />
<type>ACCOUNT(BUS)</type>
<billingAccountNumber>xxxxx</billingAccountNumber>
<billingAccountStatus>Closed</billingAccountStatus>
<telNo>xxxxx</telNo>
<restrictedVisibilityIndicator>Y</restrictedVisibilityIndicator>
- <address>
<id>xxxx</id>
<shortDescription>1, CHARNWOOD PLACE, , SOUTH ALBION STREET, LEICESTER, LE1 6JL</shortDescription>
</address>
<accountManager />
</searchResult>
</listOfSearchResults>
</searchCustomerResponse>

For security reasons have masked the private details in response.
I would try truss next.
I'd guess that you have a memory bounds error that's corrupted the stack prior to the call that appears in the core.
Topic archived. No new replies allowed.