fclose() messes up heap

Article View: comp.os.msdos.programmer

Article #1266

Back to comp.os.msdos.programmer Previous Next

#1266

From: Elan Feingold
Date: Thu, 03 Sep 1992 21:05

13 lines
1061 bytes

In a program I'm writing, after I fclose() a file, it seems to mess up the free space of the core, and I'm really not sure why.  It seems that this sequence of events messes up the memory.

1. Open file
2. Allocate and deallocate memory
3. Close file

I know that you're all going to say that I have a bad pointer or something, but I don't think that this is the case (although it might be...). I'm using BC2.0.  Is there any reported bugs with fclose, or does anyone have any similar experiences?  Thanks, very much,

 ESF 

--

Technical Details

Message-ID: <1992Sep3.210532.22036@tc.cornell.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!haven.umd.edu!darwin.sura.net!udel!rochester!cornell!batcomputer!tasha.cheme.cornell.edu!elan

Show Full Headers

Complete Article Headers

Newsgroups: comp.os.msdos.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!haven.umd.edu!darwin.sura.net!udel!rochester!cornell!batcomputer!tasha.cheme.cornell.edu!elan
From: elan@tasha.cheme.cornell.edu (Elan Feingold)
Subject: fclose() messes up heap
Message-ID: <1992Sep3.210532.22036@tc.cornell.edu>
Lines: 13
Sender: news@tc.cornell.edu
Nntp-Posting-Host: tasha.cheme.cornell.edu
Reply-To: elan@tasha.cheme.cornell.edu (Elan Feingold)
Organization: Cornell University
Date: Thu, 3 Sep 1992 21:05:32 GMT