| delorie.com/archives/browse.cgi | search |
| Date: | Thu, 1 Aug 2002 08:21:15 +0300 (IDT) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Patrick Chen <pck66 AT pd DOT jaring DOT my> |
| cc: | djgpp AT delorie DOT com |
| Subject: | Re: fread can't read a second time. |
| In-Reply-To: | <ai97kt$m10$1@news4.jaring.my> |
| Message-ID: | <Pine.SUN.3.91.1020801082028.20714B@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On Thu, 1 Aug 2002, Patrick Chen wrote: > I finally get it solved. The fault pointed by the compiler at the second > fread is not the actual place of error. Error lies somewhere in the function > of the function. There were mallocs in it and possibly multiple call of > malloc cause the fault. This usually means that some code overwrote an malloc'ed buffer, and thus corrupted the chain of memory buffers maintained internally by malloc.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |