I do not think so.

Inside the DLL, I call:

XMLPlatformUtils::Initialize();
...
XMLPlatformUtils::Terminate();

(and only once).

The first time, it does not crash, but the second time it does. And it crashes not at 
'Initialize()', but at 'DOMParser parser'.

Must I empty 'parser' variable????



On Mon, 09 July 2001, Jesse Pelton wrote:

> 
> Are you calling XMLPlatformUtils::Initialize() more than once per process?
> If so, that's your problem. See the FAQ.
> 
> -----Original Message-----
> From: john guildesh [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 09, 2001 10:38 AM
> To: [EMAIL PROTECTED]
> Subject: 'DOMParser' memory problems
> 
> 
> Hi!
> 
> Working with Visual C++ 6.0 and Xerces-C 1.4.0.
> 
> I've just created a DLL to Parse an XML document. When calling it once,
> there is no problem, but there is a problem if I call it twice.
> 
> At the second time, I get:
> 
> ("instruction xxx makes reference to the memory...")
> 
> Just when executing:
> 
> // Instantiate the DOM parser.
>     DOMParser parser;
> 
> Anybody's got experience dealing with this topic?
> Must I change my Xerces-C version???
> 
> Regards,
> 
> 
> _______________________________________________________________________
> Get a FREE email address for your WILD SIDE! Choose from over 350
> outrageous email addresses at http://www.WildEmail.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]


_______________________________________________________________________
Get a FREE email address for your WILD SIDE! Choose from over 350
outrageous email addresses at http://www.WildEmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to