Jorge, <div><br></div><div>I'm not aware of any problem with libtiff or libgeotiff likely to be responsible for this. It looks to be related to:</div><div><br> <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456303">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456303</a></div>
<div><br></div><div>Best regards,</div><div>Frank</div><div><br><div class="gmail_quote">On Wed, Oct 31, 2012 at 9:57 AM, Jorge Martin <span dir="ltr"><<a href="mailto:jormarfe@gmail.com" target="_blank">jormarfe@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<div><br></div><div><br></div><div> We have recently compiled and installed <span style="background-color:yellow"><span>libtiff</span></span>-4.0.0 and <span style="background-color:yellow"><span>libgeotiff</span></span>-1.4.0. Performing the <span style="background-color:yellow"><span>regression</span></span> tests of our tool, we have detected the following problem using <span>valgrind</span>:</div>
<div> <br></div><div><div>==32409== Invalid free() / delete / delete[] / <span>realloc</span>()</div><div>==32409== at 0x4A0730F: free (<span>vg</span>_replace_<span>malloc</span>.c:427)</div>
<div>==32409== by 0x3F55F03FAA: free_<span>mem</span> (in /lib64/<span>libc</span>-<a href="http://2.5.so" target="_blank">2.5.so</a>)</div><div>==32409== by 0x3F55F03BC1: __<span>libc</span>_<span>freeres</span> (in /lib64/<span>libc</span>-<a href="http://2.5.so" target="_blank">2.5.so</a>)</div>
<div>==32409== by 0x4803606: _<span>vgnU</span>_<span>freeres</span> (<span>vg</span>_preloaded.c:61)</div><div>==32409== by 0x3F55E32E64: exit (in /lib64/<span>libc</span>-<a href="http://2.5.so" target="_blank">2.5.so</a>)</div>
<div>==32409== by 0x3F55E1D8AA: (below main) (in /lib64/<span>libc</span>-<a href="http://2.5.so" target="_blank">2.5.so</a>)</div><div>==32409== Address 0x4e5f330 is not <span>stack'd</span>, <span>malloc'd</span> or (recently) <span>free'd</span></div>
</div><div><br></div><div>Before the installation of the new libraries we had <span>libtiff</span>-3.8.2 and <span>libgeotiff</span>-1.2.4, and this problem did not appear. </div><div><br></div>
<div>We have generated a simple source code that only links to both libraries (this main does not use any function of <span>libtiff</span> o <span>libgeotiff</span>) and the problem did not disappears(we have done this test to avoid problems with our code). </div>
<div><br></div><div>If we change this simple source code and only links to <span>libtiff</span> the problem detected by <span>valgrind</span> disappears. So the problem is related to the <span>libgeotiff</span> library. We think that the problem could be related to any static variable or global variable that is wrongly removed.</div>
<div><br></div><div>I do not know if there is a incompatibility between this versions of <span>libtiff</span> and <span>libgeotiff</span>. </div><div><br></div><div><br></div><div>Best Regards,</div>
<div><br></div><div><br></div><div>Jorge</div>
<br>_______________________________________________<br>
Geotiff mailing list<br>
<a href="mailto:Geotiff@lists.maptools.org">Geotiff@lists.maptools.org</a><br>
<a href="http://lists.maptools.org/mailman/listinfo/geotiff" target="_blank">http://lists.maptools.org/mailman/listinfo/geotiff</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>---------------------------------------+--------------------------------------<br>
I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a><br>light and sound - activate the windows | <a href="http://pobox.com/~warmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>
and watch the world go round - Rush | Geospatial Software Developer<br><br>
</div>