RE: memory corruption when deleting the SAXParser

[Jesse Pelton]

Title: Message

Well, that's definitely not the message you usually get when the runtimes are mismatched. I've never seen anything like this one. Unless this means something to someone else on the list, you may have a nasty debugging session in front of you. Have you googled for the error text?

-----Original Message-----
From: Nathan Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 3:29 PM
To: '[EMAIL PROTECTED]'
Subject: RE: memory corruption when deleting the SAXParser

Yes, I rebuilt the project from scatch using the "Rebuild All" selection in the Biuld menu.

<snip/>

Then in the output pane it has this:

memory check error at 0x013FBDE0 = 0xE8, should be 0xFD.
memory check error at 0x013FBDE1 = 0xBE, should be 0xFD.

 

-----Original Message-----
From: Jesse Pelton [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 3:10 PM
To: '[EMAIL PROTECTED]'
Subject: RE: memory corruption when deleting the SAXParser

I think that's the one. I'm having a hard time imaging why you can't release memory that you just allocated if your settings are correct. Have you rebuilt the project from scratch since making sure the settings are correct? If that doesn't help, what is the exact text of the error you get, and where does it appear?

-----Original Message-----
From: Nathan Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 2:49 PM
To: '[EMAIL PROTECTED]'
Subject: RE: memory corruption when deleting the SAXParser

If it's the one about changing the project settings to use Multithreaded DLL settings - yes.  Is that the one?