[ http://issues.apache.org/jira/browse/AXISCPP-476?page=all ] Adrian Dick resolved AXISCPP-476: ---------------------------------
Fix Version: current (nightly) Resolution: Fixed As part of the work for AXISCPP-149, the Purify tool found this memory leak and I put in a fix for it. > Memory leak throwing user-defined soap faults > --------------------------------------------- > > Key: AXISCPP-476 > URL: http://issues.apache.org/jira/browse/AXISCPP-476 > Project: Axis-C++ > Type: Bug > Components: Client - Stub > Reporter: Mark Whitlock > Fix For: current (nightly) > > In (for example) the FaultMappingTest, the user-defined soap fault is got > using > DivByZeroStruct *pFaultDetail = pSoapFault->getCmplxFaultObject() > Later in this method it throws it using throw *pFaultDetail. This fault was > new'ed by generated code called from SoapFault, but who deletes it? The > client application catches it using catch (DivByZeroStruct& e) but since it > catches a reference, not a pointer, it can't delete it either. This looks > like a memory leak to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira