[ http://issues.apache.org/jira/browse/XALANC-492?page=all ]

Dmitry Hayes updated XALANC-492:
--------------------------------

    Attachment: patch3.txt

We have a precompiled condition, depends on a definition of a macro 
XALAN_DEVELOPMENT (in the XalanMemoryManagement.hpp file). When the macro is 
defined, the non-working version of the memory manager is plugged everywhere, 
instead of the default one. That helps catching uncontrolled usage of the 
default parameters inside of the main library. I've attached a patch with the 
suggested fix. Please review! Thanks

> Various pluggable memory management bugs.
> -----------------------------------------
>
>          Key: XALANC-492
>          URL: http://issues.apache.org/jira/browse/XALANC-492
>      Project: XalanC
>         Type: Bug
>   Components: XalanC
>     Versions: CurrentCVS
>     Reporter: David Bertoni
>     Assignee: David Bertoni
>     Priority: Blocker
>      Fix For: CurrentCVS
>  Attachments: XalanDiagnosticMemoryManager.cpp, 
> XalanDiagnosticMemoryManager.hpp, XalanMemoryManagerDefault.cpp, 
> XalanMemoryManagerDefault.hpp, conf_patch.txt, patch.txt, patch3.txt
>
> There are a number of bugs with pluggable memory management.  This patch adds 
> support to the conformance test executable to detect some of these problems 
> and corrects the ones that are triggered by running the conformance tests.
> Along with this patch are four new files that define 2 new classes.

-- 
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]

Reply via email to