[ http://issues.apache.org/jira/browse/AXISCPP-343?page=comments#action_12331138 ]
John Hawkins commented on AXISCPP-343: -------------------------------------- Using STL that is exposed to the customer is not acceptable. We have seen too many instances of issues with ST on different platformsL. We also have some customers who link with compat=4 on Solaris. This means that they cannot use stl ! However, we can use stl inside the engine - just so long as it doesn't creep into the stubs. We occasionally have to sweeps to ensure that some hasn't crept in . > SIGSEGV deserializing an array of complex elements > -------------------------------------------------- > > Key: AXISCPP-343 > URL: http://issues.apache.org/jira/browse/AXISCPP-343 > Project: Axis-C++ > Type: Bug > Components: Serialization > Versions: 1.4 Final > Environment: RH9 > Reporter: Unai Uribarri > Assignee: Dushshantha Chandradasa > Attachments: siaam.wsdl > > The function Axis_Create_* (in the following example, the mapItem > object) in the stubs generated by wsdl2ws java tool generates a SIGSEGV > when tring to enlarge an array of objects > mapItem* pNew = new mapItem[nSize]; > memcpy(pNew, pObj, sizeof(mapItem)*nSize/2); > memset(pObj, 0, sizeof(mapItem)*nSize/2); > --> delete [] pObj; <-- SIGSEGV > memset clears the virtual table pointer of the mapItem objects and the delete > operator crash. -- 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
