You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Wong Hoong Shen <Ho...@capco.com> on 2002/08/27 04:22:26 UTC
Question on Deletion of Transcode strings
Hi,
I read the FAQ on why deletion of transcoded strings result in an Assertion
being thrown in Windows, but I am still rather confused by the mechanics of
the following statement:
Both your application program and the Xerces DLL must use the same *DLL*
version of the runtime library. If either statically links to the runtime
library, the problem will still occur. For example, for a Win32/VC6 build,
the runtime library build setting MUST be "Multithreaded DLL" for release
builds and "Debug Multithreaded DLL" for debug builds.
I am using v1.7.0 of Xerces C++ on Visual Studio.NET and set the linker for
my program in Debug configuration to link with xerces-c_1D.lib. I have
checked the program and confirm that it looks for xerces-c_1_7_0D.dll.
However, it still throws the Debug Heap Assertion Error. Is this the right
way to interpret the FAQ statement or am I missing something?
Thanks for your help.
Hoongshen
RE: Question on Deletion of Transcode strings
Posted by Dean Roddey <dr...@charmedquark.com>.
If you are using a version of Xerces that was built with a pre-.Net
VC++, then its going to bring in a previous runtime from what your
program is going to use, which is the V7 runtime. Use your favorite
module spelunking tool to see what runtime Xerces is bringing in. You
might have to either rebuild Xerces or get another version of it built
with the .Net version of the compiler.
-------------------------------------
Dean Roddey
The Charmed Quark Controller
droddey@charmedquark.com
www.charmedquark.com
-----Original Message-----
From: Wong Hoong Shen [mailto:Hoong.Shen.Wong@capco.com]
Sent: Monday, August 26, 2002 7:22 PM
To: 'xerces-c-dev@xml.apache.org'
Subject: Question on Deletion of Transcode strings
Hi,
I read the FAQ on why deletion of transcoded strings result in an
Assertion being thrown in Windows, but I am still rather confused by the
mechanics of the following statement:
Both your application program and the Xerces DLL must use the same *DLL*
version of the runtime library. If either statically links to the
runtime library, the problem will still occur. For example, for a
Win32/VC6 build, the runtime library build setting MUST be
"Multithreaded DLL" for release builds and "Debug Multithreaded DLL" for
debug builds.
I am using v1.7.0 of Xerces C++ on Visual Studio.NET and set the linker
for my program in Debug configuration to link with xerces-c_1D.lib. I
have checked the program and confirm that it looks for
xerces-c_1_7_0D.dll. However, it still throws the Debug Heap Assertion
Error. Is this the right way to interpret the FAQ statement or am I
missing something?
Thanks for your help.
Hoongshen