AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.10.14 07:58 "[Tiff] WIN32 _TIFFrealloc() bug?", by Ville Herva
2004.10.15 20:01 "[Tiff] WIN32 _TIFFrealloc() bug?", by Ville Herva
2004.10.15 20:09 "Re: [Tiff] WIN32 _TIFFrealloc() bug?", by Frank Warmerdam
2004.10.15 21:47 "Re: [Tiff] WIN32 _TIFFrealloc() bug?", by Ville Herva
2004.10.16 07:52 "Re: [Tiff] WIN32 _TIFFrealloc() bug?", by Andrey Kiselev
2004.10.17 16:47 "RE: [Tiff] WIN32 _TIFFrealloc() bug?", by Larry Grill
2004.10.17 17:26 "Re: [Tiff] WIN32 _TIFFrealloc() bug?", by Ville Herva

2004.10.15 21:47 "Re: [Tiff] WIN32 _TIFFrealloc() bug?", by Ville Herva

On Fri, Oct 15, 2004 at 04:09:24PM -0400, you [Frank Warmerdam] wrote:

In CVS the _TIFFRealloc implementation in tif_win32.c has been changed to the following as others have reported the same issue.

Ok.

I imagine this new implementation is in the latest libtiff 3.7.0 beta as well, which I would encourage you to try out. There are a number of known (and fixed) issues with the libtiff 3.6.1 and earlier releases.

I know. Are the Chris Evans' newest findings (http://scary.beasts.org/security/CESA-2004-006.txt) already fixed in the beta?

> tdata_t
> _TIFFrealloc(tdata_t p, tsize_t s)
> {

   void* pvTmp;

         tsize_t old;

         if(p == NULL)
                 return ((tdata_t)GlobalAlloc(GMEM_FIXED, s));

Yeah, that seems sane.

> I set the clouds in motion - turn up light and sound - activate the > windows and watch the world go round - Rush

Hmm, that's almost what Bill Gates might say...

Thanks for your prompt reply,

-- v --

v@iki.fi