[ http://issues.apache.org/jira/browse/XALANC-599?page=comments#action_12365152 ]
Dmitry Hayes commented on XALANC-599: ------------------------------------- The patch looks ok. There is an unrelated to the patch comment. The content of the destroyTranscoder method is repeating the same pattern of destroying the object and returning the memory. Later was introduced in the file xalanc/Include/XalanMemoryManagement.hpp a template "XalanDestroy" doing the job regardless the type. > Possible dangling pointer in XalanOutputStream when setting explicit encoding. > ------------------------------------------------------------------------------ > > Key: XALANC-599 > URL: http://issues.apache.org/jira/browse/XALANC-599 > Project: XalanC > Type: Bug > Components: XalanC > Versions: CurrentCVS > Reporter: David Bertoni > Assignee: David Bertoni > Priority: Critical > Attachments: patch.diff > > There is a bug where XalanOutputStream will have a dangling pointer in its > m_encoding data member, which can lead to a double-delete of the pointer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
