[ https://issues.apache.org/jira/browse/AXIS2C-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865523#comment-13865523
]
Gilles Gagniard commented on AXIS2C-1635:
-----------------------------------------
Does somebody knows what is the process to have a patch actually integrated upstream since
it looks like we are several people interested in this ? I would prefer to not have to maintain
my own axis2/c fork indefinitely ...
> Fix for various memleaks & corruptions
> --------------------------------------
>
> Key: AXIS2C-1635
> URL: https://issues.apache.org/jira/browse/AXIS2C-1635
> Project: Axis2-C
> Issue Type: Bug
> Affects Versions: 1.6.0, Current (Nightly)
> Environment: FC18 / WinXP
> Reporter: Gilles Gagniard
> Labels: patch
> Fix For: Current (Nightly)
>
> Attachments: axis2c-1635.patch, axis2c_fixes.patch
>
>
> This issue contains a patch for various memleaks / corruptions in Axis2/C.
> Each proposed fix has an attached comment in the patch describing the issue.
> In particular, it fixes :
> - a crasher introduced with r1467162 : in http_sender.c in_stream could be reused after
being freed
> - a crasher sometime happening when freeing a svc_client : in svc_client.c options should
be freed last because free callbacks for other members can tap into options (and do, see conf_ctx
for instance !)
> - a memleak in the connection_map handling in http_sender.c (key is always strdup()ed
but never freed)
> - a crasher in stream handling, happening if the incoming stream length is exactly equal
to internal buffer length
> - a memleak in om_element
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org
|