[
https://issues.apache.org/jira/browse/AXIS2C-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-872:
-----------------------------------
Attachment: diff.txt
Hi all,
I don't think that any change was made for 1.1.0 where this is in concern.
However, there can be a dangling pointer situation. You can avoid this by
applying the proposed patch, which makes it the user's responsibility to avoid
the dangling pointer situation. Refer diff.txt for proposed patch.
Regards,
Senaka
> Function axiom_document_create[Alastair FETTES]
> -----------------------------------------------
>
> Key: AXIS2C-872
> URL: https://issues.apache.org/jira/browse/AXIS2C-872
> Project: Axis2-C
> Issue Type: Bug
> Environment: Ubuntu 7.04
> Reporter: Lahiru Gunathilake
> Attachments: diff.txt
>
>
> <snippet>
> AXIS2_EXTERN
> axiom_document_t* axiom_document_create(
> const axutil_env_t* env,
> axiom_node_t* root,
> axiom_stax_builder_t* builder)
> </snippet>
> Problem: The return value of type axiom_document_t* takes responsibility for
> the memory allocated for root. Any child node that is added to root will be
> free-ed when the function axiom_document_free is called. The return value of
> type axiom_document_t* does not takes responsibility for the memory allocated
> for builder (as of v1.1.0, this seems odd, since the internal structure
> maintains a pointer to builder, but does not free builder. So this may create
> a dangling pointer situation).
> Solution: Document memory ownership for parameters and return value.
> Investigate use of pointers in internal structure.
--
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]
