On Sat, 11 Aug 2007 21:32:39 GMT, Dan Bloomquist <public21@lakeweb.com>
wrote:
XMLNODESET set= xml.GetNodeSet( _T("//Region") );
Where XMLNODESET has a std::vector member. The copy constructor was left
as default.
This is where it gets weird for me. Today I used it for the first time
in a console app and it does a copy, (the vectors are pointers and the
pointers are valid), but the memory doesn't get allocated properly in
the copied vector. I get a:
HEAP[version2_2.exe]: Invalid Address specified to RtlValidateHeap(
00D20000, 00D31270 )
When the vector goes out of scope
(_Tidy to deallocate(pointer _Ptr, size_type) )
Yet it works fine, in several places, in MFC apps. I've worked around by
setting XMLNODESET in the main scope so the output shows to the end of
the call. It doesn't crash in release, (I still get the error running
under VS but nothing stand alone.), and this is a versioning hook for a
single client that I must use.
I'm just wondering if anyone has seen something like this when switching
between memory managers. Even though I can move on I hate not
understanding where I may have a real problem.
Best, Dan.
Do you have more than one heap? Problems like this can happen if you create
and destroy objects in different modules (EXEs, DLLs), and they don't all
link to the same CRT DLL, perhaps because one module links statically to
the CRT and the other dynamically, or you're mixing debug and release
versions, etc.