From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: unload_datafile( ) freezes - new info! still need help! Date: Sat, 19 Feb 2000 21:02:51 +0200 Organization: NetVision Israel Lines: 14 Message-ID: <38AEE8DB.6B160A63@is.elta.co.il> References: <13 DOT 1a3e228 DOT 25df16f5 AT aol DOT com> NNTP-Posting-Host: ras1-p103.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 950987016 26356 62.0.172.105 (19 Feb 2000 19:03:36 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 19 Feb 2000 19:03:36 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Riddler02 AT aol DOT com wrote: > > Call frame traceback: > in function free+275 > in function _unload_datafile_object+55 > > I have very little of an idea what all this crap means. Read sections 9.2, 9.3, and 12.2 of the DJGPP FAQ list, and you will also understand this ``crap''. In general, crashes inside `free' or `malloc' are caused by some of your code overrunning an allocated buffers. You can use malloc debugging tool such as YAMD to find those bugs.