[gdal-dev] Memory corruption in PNG driver with Microsoft DebugDLLs?

Tamas Szekeres szekerest at gmail.com
Thu Apr 1 05:27:48 EDT 2010

2010/4/1 Shaw, Jonathan-P29740 <Jonathan.Shaw at gdc4s.com>

> Upon further browsing of the open tickets, I'm wondering if I'm
> experiencing the crashes, heap corruption, etc. described by
> http://trac.osgeo.org/gdal/ticket/3346.

You probably use GDAL along with one or more dependencies loaded dynamically
(like proj, libpng, libjpeg etc.) which may have been compiled against
different CRT dependencies. This may happen either by using different CRT
settings or different compiler versions when compiling the various
libraries. Having different CRT settings for the various libraries is not
necessarily a problems when the authors of the libraries follow careful
design considerations and coding practice (like making memory
allocations/deallocations within the dll boundaries etc.), but it's rarely
the case with the libraries we use. Using inhomogeneous CRT dependecies in
dependent libraries is unsupported by Microsoft either, and I've also
submitted a blogpost related to this topic here:

To avoid this situation you might want to recompile all the dependencies
with the same compiler and CRT setting which could be a nightmare in many
cases. You could alternatively use the pre-compiled binary packages / SDKs
from this location http://vbkto.dyndns.org/sdk/ which are guaranteed to
compiled satisfying with the requirements above (by using the /MD settings
for all, and the same compiler used).

Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20100401/a319dbaf/attachment.html

More information about the gdal-dev mailing list