[
https://issues.apache.org/jira/browse/AXIS2C-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Gunathilake reassigned AXIS2C-1003:
------------------------------------------
Assignee: Lahiru Gunathilake
> Memory leak in WSDL2C client code
> ---------------------------------
>
> Key: AXIS2C-1003
> URL: https://issues.apache.org/jira/browse/AXIS2C-1003
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: 1.2.0
> Environment: linux redhat as 4.0
> axis2c 1.2.0
> axis2java nigthly build
> Reporter: Simone Bordin
> Assignee: Lahiru Gunathilake
> Attachments: adb_ParSmStateRequest.c, adb_ParSmStateRequestType.c,
> axis2_stub_AppSmsService.c, valgrind.txt
>
>
> With valgrind i have found some memory leak in client generated with WSDL2C
> tool.
> In stub source code, some data pointed by "svc_name", "soap_act", "op_qname"
> are allocated but they are never free.
> Also in some adb data type, there's the same problem with variable
> "start_input_str" and "end_input_str" , "data_source".
> (in attachement files:
> axis2_stub_AppSmsService.c: line 75, 180, 188
> adb_ParSmStateRequest.c: line 249, 354, 324
> adb_ParSmStateRequestType.c: line 667, 672, 739, 744, 810, 815
> Some leaks are singalled in the the axis2c-1.2 library too.
> Attached file "valgrind.txt" is the valgrind trace after i have resolved
> leaks in generated code (except "data_source").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
