Hi all,
I think the problem is that XMLString::replicate() is inline, so the memory
will come from the heap of the particular module that's making the call.
The defeats the purpose of having XMLString::release().
Dave
Gareth Reakes
<[EMAIL PROTECTED] To: "[EMAIL PROTECTED]" <[EMAIL
PROTECTED]>
soft.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: Deleting something
returned by XMLString::replicate crashes when application is
10/01/2003 09:25 using the release build of Xerces-C++ ?
AM
Please respond
to xerces-c-dev
Hi,
sorry about the delay in replying - I needed to get some info
from
other developers and they were not around. The documentation is currently
incorrect. If you allocate with the replicate that uses the memory manager
then you cannot call release on it. Are you doing this?
Gareth
--
Gareth Reakes, Head of Product Development +44-1865-203192
DecisionSoft Limited http://www.decisionsoft.com
XML Development and Services
---------------------------------------------------------------------
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]
- Re: Deleting something returned by XMLString::replicate cr... Emmanuel Taf
- Re: Deleting something returned by XMLString::replica... Gareth Reakes
- Re: Deleting something returned by XMLString::rep... david_n_bertoni
- Re: Deleting something returned by XMLString:... Gareth Reakes
- Re: Deleting something returned by XMLStr... david_n_bertoni
- Re: Deleting something returned by X... Gareth Reakes
