[Geotiff] Problem detected in libgeotiff version 1.4.0
Jorge Martin
jormarfe at gmail.com
Wed Oct 31 11:57:41 EST 2012
Hello,
We have recently compiled and installed libtiff-4.0.0 and
libgeotiff-1.4.0.
Performing the regression tests of our tool, we have detected the following
problem using valgrind:
==32409== Invalid free() / delete / delete[] / realloc()
==32409== at 0x4A0730F: free (vg_replace_malloc.c:427)
==32409== by 0x3F55F03FAA: free_mem (in /lib64/libc-2.5.so)
==32409== by 0x3F55F03BC1: __libc_freeres (in /lib64/libc-2.5.so)
==32409== by 0x4803606: _vgnU_freeres (vg_preloaded.c:61)
==32409== by 0x3F55E32E64: exit (in /lib64/libc-2.5.so)
==32409== by 0x3F55E1D8AA: (below main) (in /lib64/libc-2.5.so)
==32409== Address 0x4e5f330 is not stack'd, malloc'd or (recently) free'd
Before the installation of the new libraries we had libtiff-3.8.2 and
libgeotiff-1.2.4, and this problem did not appear.
We have generated a simple source code that only links to both libraries
(this main does not use any function of libtiff o libgeotiff) and the
problem did not disappears(we have done this test to avoid problems with
our code).
If we change this simple source code and only links to libtiff the problem
detected by valgrind disappears. So the problem is related to the
libgeotifflibrary. We think that the problem could be related to any
static variable
or global variable that is wrongly removed.
I do not know if there is a incompatibility between this versions of libtiffand
libgeotiff.
Best Regards,
Jorge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/geotiff/attachments/20121031/5267a5d7/attachment.htm
More information about the Geotiff
mailing list