AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2008.12.17 20:54 "[Tiff] Deleting tags from a directory", by Frank Warmerdam
[...]
2008.12.18 22:05 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.19 02:26 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.19 03:12 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
[...]

2008.12.19 02:26 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam

Is anyone aware of any other serious issues with the 3.9 branch? If not, I'd like to produce a 3.9.0 release candidate for testing.

It would be nice if libtiff would run clean with 'valgrind'. While I am not aware of any memory leaks, it seems that TIFF directories are accessed/written which contain uninitialized data and this causes 'valgrind' to complain about use of uninitialized data. The workaround may be as simple as doing a 'memset' on directory structures immediately after they are allocated.

Bob,

I tried running tiff2rgba and tiffcp on a file or two under valgrind and I didn't see any reported problems. Can you be more specific about the circumstances? Is this something you would like to address? I'm somewhat ambivalent about it.

Best regards,
--
---------------------------------------+--------------------------------------

I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam

and watch the world go round - Rush    | Geospatial Programmer for Rent