[gdal-dev] OCI driver and Heap Corruption under Visual C++

[Mateusz Loskot]

Tamas Szekeres wrote:
> Mateusz,
> 
> I gave up monkeying with MDd after spending a couple of days to
> eliminate these strange effects caused crashes in the windows builders
> at the buildbot. My suspicion is that in this case we inevitably use
> dll dependencies with different CRT setting may lead to unpredicted
> problems (OCI lib might have been compiled with /MD I think). I guess
> if you could compile all of the related dll with /MDd setting you
> would probably gain a more stable debug package then, however I
> consider we less likely need to debug into the CRT libraries itself,
> so this is what you shouln't worry about. Sleep well :-)


Tamas,

Yes, you're probably right. GDAL is built with shared copy of CRT (/MD)
but as I see in Oracle samples for OCI, they use /MT flag and separate 
copies of CRT.

Mixing /MD and /MT may lead to big problems.

Hmm, looks like not solvable problem for OCI.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org