Hi !
The memory manager is generated with XMLPlatformUtils::Initialize() function .
You can't make any call to XalanDOMString contractors before you have called to the both "Initialize" functions.
Thanks!
Dmitry Hayes
XSLT Development
IBM Toronto Lab
Phone: 905-413-3820
E-mail: [EMAIL PROTECTED]
| "Paul Thomas (JIRA)"
<[email protected]>
03/08/2005 11:07 AM
|
|
Memory Management Issues: The assert subroutine failed: m_memoryManager != 0
----------------------------------------------------------------------------
Key: XALANC-462
URL: http://issues.apache.org/jira/browse/XALANC-462
Project: XalanC
Type: Bug
Components: XalanC
Versions: 1.9
Environment: Platform: AIX Software: Xerces2.6 & Xalan1.9
Reporter: Paul Thomas
I am currently upgrading our versions of xalan and xerces and have begun testing. After a few initial build problems, which have been addressed in a previous post. I have encountered a problem at runtime with the memory manager. An assertion error is always thrown regardless:
The assert subroutine failed: m_memoryManager != 0, XalanVector.hpp Line 944.
This error is invoked when I try and create an instance of a XalanDOMString(), as I noticed it retrieves a default memory manager within its parameter list. The exact syntax I use in the call is:
XalanDOMString string1 = XalanDOMString(text); // text being of the type const char *.
What puzzles me is that I do have the following calls in my code:
XMLPlatformUtils::Initialize()
XalanTransformer::initialize()
With the first generating a default memory manager?
If anyone could provide me with any guidance I would appreciate it. I hope I have posted this message onto the correct forum also.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
