Core file in new funtion

Hi,

I have a core dump which does not seem to be a problem with my code. Can you please explain is this a problem with the programming and what is the probable cause for these kind of core dumps ?

Its on solaris 8. CC: Sun WorkShop 6 update 1 C++ 5.2 Patch 109508-03 2001/04/07

libc.so.1`_malloc_unlocked+0x164(18c, 6976652c, febbc008, 190, 319978, 0)

libc.so.1`malloc+0x20(18c, 1a, 10, 1, 0, 95)

libCrun.so.1`__1c2n6FI_pv_+0x28(18c, bcf3, 13740, fb70cc94, fecaa8d4, 18c)// This when demangled shows new(unsigned)

libeai.so.3`__1cSEAC_IPC_ConnectionHConnect6MpnXEAC_IPC_Connection_Pool__pnPEAC _IPC_Session__+0x20c(fb70d100, 0, ffffffff, bcf3, 706c, fb70d22c)

libeai.so.3`__1cSEAC_IPC_ConnectionHConnect6M_pnPEAC_IPC_Session__+0x2c(fb70d10 0, 1938fc, 0, 0, fecaa8d4, 37b740)

__1cWEAM_MML_CommandSessionVTerminateSubscription6M_i_+0xb4(30fa40, 1a8ef0,

1a8ef0, 18378a, 0, 30fa40)

__1cWEAM_MML_CommandSessionQterminateSession6M_v_+0xa8(30fa40, 1e4, 0, 307a88,

28c6bc, 0)

__1cQCommsManagerImplQterminateSession6ML_v_+0x544(297350, 1e4, 34c3d8, fb70d95c, 1eb7f8, 0)

__1cHPOA_EACDEAIOCommandSessionR_terminateSession6FpvrnVCORBA_MarshalInBuffer_p kcrnPVISReplyHandler__v_+0x64(297350, 34c3d8, 1f5b30, fb70da70, 1eb7f0, 297350)

liborb_r.so`__1cLVISSkelInfoHexecute6MrknOVISGIOPRequest_rnVCORBA_MarshalInBuff er_rnPVISReplyHandler__v_+0x94(1575c0, 1f5b30, 34c3d8, 298d00, fe948ebc, fb70da70)

liborb_r.so`__1cWVISGIOPProtocolAdapterL_do_request6MpnOVISGIOPRequest_pnOVISGl obalTable__v_+0x380(299660, 34c630, fb70da70, fe948ebc, 1, 1f5b30)

liborb_r.so`__1cWVISGIOPProtocolAdapterR_dispatch_message6MpnOProtocolEngineHMe ssage_pnOVISGlobalTable__v_+0x104(29ba20, 29ba50, 34bd50, fe948ebc, 34c6f8,

29ba20)

liborb_r.so`__1cXVISThreadPoolDispatcherHdo_work6MpnOProtocolEnginePProtocolAda pter_rl_v_+0x138(34bd50, 0, 1f7c28, 29ba20, 295a70, 0)

liborb_r.so`__1cRVISDispatchWorkerHdo_work6MpnOVISThreadLocal__v_+0x34(fb70dbe4 , 1f7c20, 0, 34bd50, 0, 0)

liborb_r.so`__1cNVISThreadPoolN_perform_task6MpnOVISTPoolWorker__v_+0x170(

fb70dc54, 3098e0, fb70dc4c, fec3379c, 1, 34bd50)

liborb_r.so`__1cOVISTPoolWorkerFbegin6M_v_+0x18(3098e0, fb70dd18, 0, fe948ebc,

11, fb70dd39)

libvport_r.so`__1cJVISThreadG_start6Fpv_1_+0x5c(3098e0, fdda5d38, 1, ff33e218, 0, 2)

libthread.so.1`_thread_start+0x40(3098e0, 0, 0,

Thanks

[2458 byte] By [moh_muj] at [2007-11-26 10:50:35]
# 1
Missed to add that its a multi threaded application.
moh_muj at 2007-7-7 3:03:13 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2
It's almost impossible to tell without seeing the source code.I'd recommend testing with a memory checking tool; either purify if you have a licence, or the memory checker builtin to dbx, or both.Paul
Paul_Floyd at 2007-7-7 3:03:13 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 3
Take a look at this forum article. http://forum.sun.com/jive/thread.jspa?forumID=305&threadID=71164You are using an obsolete and unsupported compiler. You shoudl upgrade to Sun Studio 11, which is free for all uses. http://developers.sun.com/sunstudio
clamage45 at 2007-7-7 3:03:13 > top of Java-index,Development Tools,Solaris and Linux Development Tools...