home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!csd4.csd.uwm.edu!markh
- From: markh@csd4.csd.uwm.edu (Mark)
- Newsgroups: comp.lang.c
- Subject: Unsolveable bug
- Date: 29 Dec 1992 17:34:38 GMT
- Organization: Computing Services Division, University of Wisconsin - Milwaukee
- Lines: 14
- Message-ID: <1hq27eINNjv@uwm.edu>
- NNTP-Posting-Host: 129.89.7.4
-
- I've run into an unsolveable bug. The bug comes from no visible error, it
- disappears when searched for under a debugger, and it's likewise non-existent
- when the same program is run under other platforms and compilers. And it
- doesn't involve anything having to do with timing of any sort.
-
- It appears on the DOS port of the program and causes the machine to crash
- immediately after a call to malloc(). The malloc call is the ANSI-compatible
- call, declared with the <stdlib.h> header. The particular usage leading to
- the crash is (as determined by traces): malloc(16), malloc(16), malloc(20), ...
- with no intervening free() calls. All calls to malloc() return valid pointers.
- Checking the memory usage reveals no corruption or access out of bounds.
-
- The compiler creating the problem has had reliable error-free performance
- with other similar programs.
-