While the linux/g++ version is building... I'm not sure it's a simple matter of deleting a transcoded string. For example, the following code works fine:
<snippet>
std::string s("froggie");
{
XalanDOMString ds = TranscodeFromLocalCodePage(s.c_str(), s.size());
}
//CharVectorType cv = TranscodeToLocalCodePage(ds); // int3
</snippet>
Wouldn't this exhibit the same problem if it were due to run-time library
conflicts?
David N
Bertoni/Cambridge To:
[email protected]
/IBM cc:
<david_n_bertoni@ Subject: Re: Shouldn't this
work?
us.ibm.com>
07/24/2002 01:41
PM
Do you have run-time library conflicts? See:
http://xml.apache.org/xerces-c/faq-parse.html#faq-23
Dave
Dick.
[EMAIL PROTECTED] To:
[email protected]
cc: (bcc: David N
Bertoni/Cambridge/IBM)
07/24/2002 12:03 Subject: Shouldn't this
work?
PM
Xalan CVS tip revisions downloaded 22 July 02. Built against xerces 1.7.0
with VC 6.0, SP5 on XP Prof.
The following code yields an int3:
<snippet>
std::string s("froggie");
XalanDOMString ds = TranscodeFromLocalCodePage(s.c_str(), s.size());
CharVectorType cv = TranscodeToLocalCodePage(ds); // int3
</snippet>
HEAP[myprog.exe]: Invalid Address specified to RtlValidateHeap( 00EA0000,
01159D70 )
