Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!mcsun!ukc!icdoc!pj
From: pj@doc.ic.ac.uk (Paul Jarvis)
Newsgroups: comp.lang.c
Subject: Re: Does TC's farrealloc have a bug?
Message-ID: <1991Jun21.152700.25820@doc.ic.ac.uk>
Date: 21 Jun 91 15:27:00 GMT
References: <1991Jun19.083945.8921@ucthpx.uct.ac.za> <6574@ns-mx.uiowa.edu>
Organization: Department of Computing, Imperial College, University of London, UK.
Lines: 9
Nntp-Posting-Host: swan.doc.ic.ac.uk


I have recently had a report of problems using huge far pointers and allocating
and freeing memory. The problem appeared to be that the free process did not
work hence memory got lost. The compiler was Turbo C (sorry version not known).
Changing to Borland C++ compiler with identical code - i.e. the same program
no problem. My conclusion is that there may be some problems with allocating
large memory chuncks but I sure don't want to try to prove it.
                           Paul
                        (pj@doc.ic.ac.uk)