From: "Rafal 'Raf256' Maj" <admin AT raf256 DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Memory trash in exe ?
Date: 30 May 2002 19:31:23 GMT
Organization: news.onet.pl
Lines: 14
Sender: raf256 AT poczta DOT onet DOT pl@62.233.182.179
Message-ID: <Xns921EDB82244E5adminraf256com@213.180.128.20>
References: <Xns921ED110825F7adminraf256com AT 213 DOT 180 DOT 128 DOT 20> <200205301841 DOT g4UIfFB21472 AT envy DOT delorie DOT com>
NNTP-Posting-Host: 62.233.182.179
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 8bit
X-Trace: news.onet.pl 1022787083 19429 62.233.182.179 (30 May 2002 19:31:23 GMT)
X-Complaints-To: abuse AT onet DOT pl
NNTP-Posting-Date: 30 May 2002 19:31:23 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

DJ Delorie <dj AT delorie DOT com> wrote in 
news:200205301841 DOT g4UIfFB21472 AT envy DOT delorie DOT com:

> This is a "feature" of DOS and Windows.  When you seek in a file, the
> holes are filled from an uninitialized buffer.  BFD does these types
> of seeks, so you see the junk in objects and executables.

can BFD take in cosider this bug in Dos/Win and fix it ? it doesnt sound 
difficult - just write zero's instead of seek


-- 
Rafał 'Raf256' Maj
GG-1175498