Sounds like a heap collision between different memory managers. Transcode allocates the char* buffer returned to your program. If your program utilizes a different memory manager that that of Xerces, you are effectively releasing memory that you didn't allocate.
To the best of my knowledge, Xerces has not implemented a function through which you can return memory that was allocated by Xerces. HTH, Don At 02:00 PM 12/28/2001 -0500, you wrote: >Is there anything special about the char * returned by >DOMString::transcode? I am using DOMString in JNI (which is probably part >of the problem) -- but I am getting some fairly abnormal behavior. I am >wondering if there is anything in particular I have to do to dispose of >the pointer returned by the above mentioned function. > >My applet terminates unexpectedly when I call delete myDomString;. The >error is like so: > >An unexpected exception has been detected in native code outside the VM. >Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0xf586689 >Function name=std::bad_exception::what >Library=C:\WINNT\system32\ddjni.dll >Source file = M:\pro 7 builds\MSL\MSL_C\MSL_Common\Src\alloc.c : 807 > >Deletion of other locally-allocated pointers works fine. > >Any ideas? > >Thanks, > >Toby >-- >Tobias McNulty >Data Description, Inc. >840 Hanshaw Road, Suite 9 >Ithaca, NY 14850 >Phone: (607) 257-1000 >E-mail: [EMAIL PROTECTED] >Web: www.datadesk.com > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
