[ http://issues.apache.org/jira/browse/XALANC-599?page=comments#action_12365143 ]
Joe Kesselman commented on XALANC-599: -------------------------------------- Traditional C solution is for callers who want that behavior to use a wrapper macro, along the lines of #define zap(x) (free(x),x=null) Something similar could certainly be implemented for C++. But I think it's beyond the scope of destroyTranscoder per se. (IBM's C compilers used to come with a bunch of safe/debugging heap tools, including the ability to not only null out pointers but to set/clear released memory blocks and do other things to try to detect reference errors. I don't know whether that sort of capability still ships with the C++ version.) > 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]
