AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2012.09.06 15:30 "[Tiff] Managing the buffer", by
2012.09.06 17:10 "Re: [Tiff] Managing the buffer", by
2012.09.07 09:21 "Re: [Tiff] Managing the buffer", by
2012.09.07 09:57 "Re: [Tiff] Managing the buffer", by Joris Van Damme
2012.09.07 10:26 "RE: [Tiff] Managing the buffer", by
2012.09.07 11:01 "Re: [Tiff] Managing the buffer", by Joris Van Damme
2012.09.07 13:12 "RE: [Tiff] Managing the buffer", by
2012.09.07 13:39 "Re: [Tiff] Managing the buffer", by Joris Van Damme
2012.09.07 13:45 "RE: [Tiff] Managing the buffer", by
2012.09.07 14:16 "Re: [Tiff] Managing the buffer", by Bob Friesenhahn
2012.09.07 14:31 "Re: [Tiff] Managing the buffer", by
2012.09.07 15:52 "Re: [Tiff] Managing the buffer", by Bob Friesenhahn
2012.09.07 11:25 "Re: [Tiff] Managing the buffer", by

2012.09.07 14:31 "Re: [Tiff] Managing the buffer", by

It has to be cross platform including Windows and I think it may have to be archaic. We're still stuck on RedHat 5 for now on the Linux side, I'm not sure what the situation of the Windows libraries is. Are you actually saying that the implementation of _TIFFmalloc has changed?

> -----Original Message-----
> From: Bob Friesenhahn [mailto:bfriesen@simple.dallas.tx.us]
> Sent: 07 September 2012 15:17
> To: Atwood, Robert (DLSLtd,RAL,DIA)
> Cc: info@awaresystems.be; tiff@lists.maptools.org
> Subject: Re: [Tiff] Managing the buffer

On Fri, 7 Sep 2012, Robert.Atwood@diamond.ac.uk wrote:

I don't see how to do it without altering the code of libtiff, as far as I can tell _TIFFMalloc just calls malloc() (on unix) and I suppose that, at compile time, the build system uses a different allocation routine depending upon the platform it's on. It would be better for me not to use TIFF than to require having a special 'hacked' version of libtiff!

What operating system are you using?

> Some operating systems allow easily replacing the memory allocators at run-

> time by telling the system to load a library before loading other libraries.

For example, under Solaris, Linux, and FreeBSD, this can be done via the LD_PRELOAD environment variable. Replacing the underlying memory allocator is a common use for this functionality.

If you are experiencing issues with the memory allocator you could try alternate ones like libumem.

--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom