From:	"John S. Fine" <johnfine AT erols DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GCC bugs
Date:	Wed, 19 Jan 2000 17:17:27 -0500
Lines:	30
Message-ID:	<388637F7.7EB3@erols.com>
References:	<01bf611a$9c6e9500$LocalHost AT alex> <3883BCC2 DOT 2CC1DCD9 AT a DOT crl DOT com> <01bf61c3$70f0a7c0$LocalHost AT alex> <Pine DOT SUN DOT 3 DOT 91 DOT 1000119113628 DOT 9609M-100000 AT is> <01bf627f$0b8075c0$LocalHost AT alex> <3885FC3A DOT E2827604 AT is DOT elta DOT co DOT il>
Mime-Version:	1.0
X-Trace:	QopJyCHhEapjwkI9g1QRLtg253cIG16QuBdtzAVXgI0=
X-Complaints-To:	abuse AT rcn DOT com
NNTP-Posting-Date:	19 Jan 2000 22:20:33 GMT
X-Mailer:	Mozilla 3.01 (Win95; U)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii wrote:
> 
> "Alexei A. Frounze" wrote:

> > I know COFFs very well.
> 
> I didn't say you didn't know COFF.  I just said that a bug is generally not
> smart enough to know about COFF.

  Let me jump in here with a guess.

  Don't be offended Alexei, and I might easily be wrong, but I think
this problem is that you don't know COFF format well enough.

  It is possible in COFF format to have unused space within the
COFF file.  If a file with unused space is generated then that
unused space will have whatever bytes were left over in RAM in
some buffer the compiler allocated but incompletely used.

  The bug you reported, perfectly fits what you would see if
you use a COFF dumper that tries to interpret the entire file
on a file that contains garbage in unused spaces.

  The question is easy to resolve.  Just use someone else's
COFF dumper on the same two files.  If doesn't see the same
difference then the difference is in an unused part of the
file.
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/

- Raw text -