Message-ID:	<3F1BE5F0.3030906@psy.kuleuven.ac.be>
Date:	Mon, 21 Jul 2003 15:09:04 +0200
From:	Peter Claessens <peter DOT claessens AT psy DOT kuleuven DOT ac DOT be>
User-Agent:	Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language:	nl-BE,en
MIME-Version:	1.0
To:	djgpp <djgpp AT delorie DOT com>
Subject:	Re: malloc/free blues
References:	<3F156434 DOT 3000508 AT psy DOT kuleuven DOT ac DOT be> <uu19m75gm DOT fsf AT elta DOT co DOT il> <3F159AC9 DOT 4010402 AT student DOT kuleuven DOT ac DOT be> <3405-Thu17Jul2003062928+0300-eliz AT elta DOT co DOT il> <3F16A565 DOT F77DA70E AT psy DOT kuleuven DOT ac DOT be> <9003-Thu17Jul2003180038+0300-eliz AT elta DOT co DOT il>
In-Reply-To:	<9003-Thu17Jul2003180038+0300-eliz@elta.co.il>
X-Virus-Scanned:	by KULeuven Antivirus Cluster

Just a remark about this:

>  - download djlsr203.zip, extract the module malloc.c from it, and
>    paste its code into your program's sources;
>  
>
I thought it would be a good idea to set the #DEBUG preprocessor symbol 
in that file to 1. Apparently it wasn't.  I get the ugliest crashes at 
startup of the program, apparently based on a segmentation fault (at 
least that's what GDB says) in the beginning of the program, before any 
output is sent to the screen, resulting in blue screens etc in win98. I 
guess the debugging code isn't meant to run under windows? Or is it 
really indicating something about my program being very wrong?
In case it would matter, the int _crt0_startup_flags =  
_CRT0_FLAG_FILL_SBRK_MEMORY |  _CRT0_FLAG_FILL_DEADBEEF; is still set.



Cheers,
P

- Raw text -