-
2012.09.06 17:10 "Re: [Tiff] Managing the buffer", by John
-
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:25 "Re: [Tiff] Managing the buffer", by John
-
2012.09.07 09:57 "Re: [Tiff] Managing the buffer", by Joris Van Damme
-
2012.09.07 09:21 "Re: [Tiff] Managing the buffer", by
2012.09.07 14:16 "Re: [Tiff] Managing the buffer", by Bob Friesenhahn
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.
Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/