[
https://issues.apache.org/jira/browse/AXIS2C-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548751
]
Senaka Fernando commented on AXIS2C-808:
----------------------------------------
Yes,
I think you are referring to a compiler flag. This should be the approach that
we should opt as there are several inconsistencies between libxml2 and
guththila and since we have no control over libxml2's implementations unlike
guththila, we need to have a mechanism to realize the difference at compilation.
Great job!
Regards,
Senaka
> Incompatible between Guththila and Libxml
> -----------------------------------------
>
> Key: AXIS2C-808
> URL: https://issues.apache.org/jira/browse/AXIS2C-808
> Project: Axis2-C
> Issue Type: Bug
> Components: xml/om
> Affects Versions: Current (Nightly)
> Environment: Ubuntu
> Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff
>
>
> In om_stax_builder.c it calls parsers get_value and get_prefix like methods
> to get the parts of the xml.But when it wants to free those axis2_char_t* it
> simply calls the axiom_xml_reader_free method.But since Guththila and Libxml2
> implementations are different , with Guththila it doesn't actually delete the
> malloc char*.To resolve this we can't simply use AXIS2_FREE to delete with
> both parsers because libxml2 gives those parts without doing malloc.Then we
> have to use some macro definition and decide whether built with guththila or
> not and use seperate methods to delete those char*.If we simply ignore this
> it cause a big memory leak with Guththila.It's around 3000bytes for a simple
> xml.
> Regs
> lahiru
--
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]
