From: "Rafal 'Raf256' Maj" <rafal AT raf256 DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: strange content in compiled file
Date: 16 Jun 2002 14:51:14 GMT
Organization: news.onet.pl
Lines: 20
Sender: raf256 AT poczta DOT onet DOT pl@62.233.182.179
Message-ID: <Xns922FAC198699Craf256com@213.180.128.20>
References: <aehvo9$73br1$1 AT ID-43990 DOT news DOT dfncis DOT de> <Xns922F96A66B6F9raf256com AT 213 DOT 180 DOT 128 DOT 20> <3d0ca403_2 AT news DOT bluewin DOT ch>
NNTP-Posting-Host: 62.233.182.179
X-Trace: news.onet.pl 1024239074 17520 62.233.182.179 (16 Jun 2002 14:51:14 GMT)
X-Complaints-To: abuse AT onet DOT pl
NNTP-Posting-Date: 16 Jun 2002 14:51:14 GMT
User-Agent: Xnews/5.03.24
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Vinzent Hoefler <JeLlyFish DOT software AT gmx DOT net> wrote in
news:3d0ca403_2 AT news DOT bluewin DOT ch: 

>>yes, this is a bug in MsDos / Windows that don't fill with zero's new 
>>blocks of memory / diskspace
> And so why does the linker output a lot of bytes of uninitialized
> memory? Isn't it supposed to output just the things it needs to create
> the executable?

yes, I don't know exacly but this is AFAIK needed to reserve stack space, 
and to create proper format of .exe

ther is some way to repair this - by changing binutils, but unfortunatly I 
don noth have now time and skills to do this, ask DJ how to fix it.

I'm preparing a small wark-around for this bug :)


-- 
Rafał 'Raf256' Maj