Developers,
Since we are still having some collisions once in a while, should we
rename the functions such as FreeMemory in the code to
_dxf_FreeMemory? I know this is ugly, but if we are going to continue
to import other libraries--this might be the best fix.
Just a thought--I could perform a global search and replace with just
a few hours of work.
David
At 5:06 PM -0400 6/14/00, Suhaib Siddiqi wrote:
> I still can not save Image Magick supported formats using 5.2. I have
debugged the problem to FreeMemory() in TemporaryFilename. I can not seem
to step through FreeMemory. I commented out FreeMemory to see what would
happen and then I get another error at the next FreeMemory at the end of
DestroyImage (line 2201 in image.c) called by SetImageInfo (from
ReadImage).
I had been handeling this problem different way.
I always compiled my own ImageMagick libraries, and changed FreeMemory to
_FreeMemory
everywhere in ImageMagick Code.
At FreeMemory, it appears to be accessing memory.c line 243 in libdx with
garbage about flist, not FreeMemory on line 121 of magick/memory.c. Would
order of libraries matter or should I try renaming libdx/memory.c to say
dxmemory.c?
I think everything is -n32, but could that be a source of the problem if
somewhere an o32 library is being used?
Anyone have DX working from CVS with IM 5.2 on an SGI?
I am headed out of town, so I will not be able to look into this further
until Monday.
Jeff
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
