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

Tamas Szekeres szekerest at gmail.com
Sat Aug 30 17:41:09 EDT 2008


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 :-)

Best regards,


2008/8/30 Mateusz Loskot <mateusz at loskot.net>:
> Tamas Szekeres wrote:
>> Mateusz,
>> I could only mention http://trac.osgeo.org/gdal/ticket/2230 in this
>> topic but I'm not sure if it is related to this problem.
>> I have been using OCI compiled with MSVC2005 a couple of months ago,
>> but didn't find such issue. However I'm using /MD instead of /MDd most
>> of the time.
> Tamas,
> Thanks for reminding me this ticket.
> Yes, indeed it seems to be related.
> However, as we are not linking against /MDd I suppose I shouldn't waste time
> on fixing it, though I'm not sure if I can't sleep well knowing GDAL might
> crash  ;-)
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> Charter Member of OSGeo, http://osgeo.org

More information about the gdal-dev mailing list