Xerces uses either the Debug multithreaded DLL run-time or the
multithreaded DLL run-time.   _Every_ module must use the appropriate
multithreaded DLL run-time.

Make sure that all of your modules are linking against the DLL run-time.  I
guarantee that if you're getting this error message, you're mixing
run-times.

Dave



                                                                                       
                                              
                    Lyman                                                              
                                              
                    Neuschaefer             To:     "'[EMAIL PROTECTED]'" 
<[EMAIL PROTECTED]>                    
                    <lneuschaefer@te        cc:     (bcc: David N Bertoni/CAM/Lotus)   
                                              
                    comac.com>              Subject:     RE: Deallocating memory 
allocated by XMLString::transcode on Win3      2    
                                            platform                                   
                                              
                    04/18/2001 11:42                                                   
                                              
                    AM                                                                 
                                              
                    Please respond                                                     
                                              
                    to xerces-c-dev                                                    
                                              
                                                                                       
                                              
                                                                                       
                                              



Sorry for not having consulted the FAQ.  How silly of me.

The FAQ says that the problem is due to mixing of runtimes,
as you say.  However, I'm using the Debug version of the Xerces
library, as well as the Debug version of the CRT.  What else might
be the problem?

-----Original Message-----
From: Erik Rydgren [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 8:56 AM
To: [EMAIL PROTECTED]
Subject: RE: Deallocating memory allocated by XMLString::transcode on
Win32 platform


You are mixing runtimes. Read the FAQ.

/ Erik Rydgren

-----Original Message-----
From: Lyman Neuschaefer [mailto:[EMAIL PROTECTED]]
Sent: den 18 april 2001 16:48
To: '[EMAIL PROTECTED]'
Subject: Deallocating memory allocated by XMLString::transcode on Win32
platform


Greetings,

The documentation indicates that XMLString::transcode() dynamically
allocates
memory to contain the content of the returned buffer and that it's the
responsibility
of the user to deallocate such memory.  However, using delete and delete[]
cause
my application to fatal on an assert which insists that the memory be be
allocated
on a 'local' heap.

With Rational Purify I have confirmed that failure to delete the return
value from
transcode results in a memory leak.  How can I deallocate such memory on
win32?

Thanks for your help

Lyman Neuschaefer

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

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

Reply via email to