AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.04.28 02:38 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 04:32 "Re: VC++ Release build causes problems", by Roy Darrall
2000.04.28 06:16 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 06:25 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 09:19 "VC++ Release build causes problems", by John Aldridge
2000.04.28 17:49 "Re: VC++ Release build causes problems", by Daniel McCoy
2000.04.29 00:27 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 17:27 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 18:33 "Re: VC++ Release build causes problems", by Jan Nijtmans
2000.04.28 20:39 "Re: VC++ Release build causes problems", by Daniel McCoy

2000.04.28 17:49 "Re: VC++ Release build causes problems", by Daniel McCoy

Me again. I just loaded the strike image in The Gimp and saved it as an LZW compressed image and a non-compressed image. The non-compressed image works PERFECTLY under both debug and release builds. The LZW compressed image screws up royally under the release build but works fine in debug. I hate to go out on a limb here (cuz' I've been wrong in the past), but this clearly seems to be a problem in the library

Quite to the contrary,
this is clearly a compiler optimizer bug.

The LZW compression in libtiff has been working for years on dozens of different compilers and operating systems. I myself have built the library using at least twelve different compilers for software that relies heavily on LZW RGBA images.

I have not had an LZW compression since the library was young back in the early 90's

Turn off optimization in your compiler and this will go away.

Then call MicroSoft (as if that will do any good.)

Dan McCoy Pixar mccoy@pixar.com