Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 37850 invoked from network); 20 Sep 2005 04:33:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Sep 2005 04:33:01 -0000 Received: (qmail 45165 invoked by uid 500); 20 Sep 2005 04:33:00 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 45048 invoked by uid 500); 20 Sep 2005 04:33:00 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 45035 invoked by uid 99); 20 Sep 2005 04:32:59 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2005 21:32:59 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id EF1DB123 for ; Tue, 20 Sep 2005 06:32:27 +0200 (CEST) Message-ID: <1771627320.1127190747947.JavaMail.jira@ajax.apache.org> Date: Tue, 20 Sep 2005 06:32:27 +0200 (CEST) From: "Dushshantha Chandradasa (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXISCPP-343) SIGSEGV deserializing an array of complex elements In-Reply-To: <135807434.1104403030193.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXISCPP-343?page=comments#action_12329941 ] Dushshantha Chandradasa commented on AXISCPP-343: ------------------------------------------------- from the Mailing list: Dushshantha Chandradasa wrote: >Hi All, >Could somebody please explain why do we use a virtual destructor in >complex type auto generated classes for RPC style? > > In my understanding, it is not a problem to use the virtual destructors. But the problem is that we use both memset, followed by delete[] on the same object. I think we got to do only one of those and see if there are memory leaks. using delete[] without memset and checking for leaks would reveal whether delete[] alone would take care of memory cleaning. Thanks, Samisa... > 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