axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Gagniard (JIRA)" <>
Subject [jira] [Comment Edited] (AXIS2C-1635) Fix for various memleaks & corruptions
Date Wed, 17 Apr 2013 13:59:16 GMT


Gilles Gagniard edited comment on AXIS2C-1635 at 4/17/13 1:58 PM:

Hello !

This is really strange ... I cannot reproduce this issue.
With both a SSL-enabled and a SSL-disabled build of current axis2-C trunk (plus this patch),
I don't have any crash with the echo sample, and valgrind/memcheck doesn't report any error.

In particular, I don't understand how freeing options *later* in svc_client.c could cause
a memory corruption.

If you apply the rest of the patch while leaving out the move of options free in svc_client.c,
do you still get a coredump ?

Many thanks for your time trying this :)
      was (Author: gillesgagniard):
    Hello !

With a SSL-enabled build of current axis2-C trunk (plus this patch), I don't have any crash
with the echo sample, and valgrind doesn't report any error.

I will retry with a SSL-disabled build then ...
> Fix for various memleaks & corruptions
> --------------------------------------
>                 Key: AXIS2C-1635
>                 URL:
>             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_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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message