DO NOT REPLY [Bug 49264] crash in DSIGKeyInfoX509::appendX509Certificate

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=49264

Scott Cantor <ca...@osu.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|C++ 1.6.0                   |cvs

--- Comment #1 from Scott Cantor <ca...@osu.edu> 2010-05-07 13:01:50 EDT ---
There are a ton of cases in the code where an ArrayJanitor (which performs a
delete []) is used to dispose of results allocated inside Xerces. Technically
that requires using XMLString::release, but in practice they're the same most
of the time.

Unless you're using a custom memory manager in Xerces, I think it's a
platform-specific problem that doesn't show up very often, but it is a bug.

The problem with fixing them all easily is that unlike my own code, which has
auto_ptr-like classes for Xerces results, this code I inherited maintenance of
does not. So explicitly freeing results introduces lots of exception-handling
based leak possibilities, so it takes a lot of time to fix.

I may just port over my code for fixing this and start using it instead of
ArrayJanitor.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.