X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Authentication-Warning:	mcomail02.maxtor.com: iscan owned process doing -bs
X-MimeOLE:	Produced By Microsoft Exchange V6.5.7226.0
MIME-Version:	1.0
Subject:	RE: Executable corruption with UPX v1.24 and v1.25
Date:	Wed, 16 Nov 2005 09:29:39 -0700
Message-ID:	<71078E41DDE3E541B024832F34BC3D0DA3081B@cowexc03.corp.mxtr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	Executable corruption with UPX v1.24 and v1.25
Thread-Index:	AcXqgxrSjRBGeAD7Q1aMDFCuTu6+2QAQoHdw
From:	"Schumacher, Gordon" <gordon_schumacher AT maxtor DOT com>
To:	"Andris Pavenis" <pavenis AT latnet DOT lv>
Cc:	"DJGPP List \(E-mail\)" <djgpp AT delorie DOT com>
X-OriginalArrivalTime:	16 Nov 2005 16:29:39.0804 (UTC) FILETIME=[F107C9C0:01C5EACA]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id jAGGTjiZ014565

# From: Andris Pavenis [mailto:pavenis AT latnet DOT lv]
# Sent: Wednesday, November 16, 2005 12:55 AM
# To: Schumacher, Gordon
# Cc: DJGPP List (E-mail)
# Subject: Re: Executable corruption with UPX v1.24 and v1.25
# 
# Known problem. Long time ago I used UPX (perhaps version 1.23) to 
# compress release binaries of GCC which I uploaded for DJGPP
# distribution. No one complained, but after some time I found that
# unpacked gcc.exe crashes. A safeguards were added beginning with
# UPX-1.24 to prevent compression of binaries generated by incompatible
# binutils versions (or GCC versions). So it seems strange that You
# succeeded to compress executables with UPX-1.24 and 1.25 at all.

Hmm... is there any information anywhere as to what those incompatible
versions of binutils and gcc might be?  Because we've been using UPX
to compress our executables successfully for more than four years,
starting with gcc 2.95 (I don't recall which binutils that was, four
years ago) and now using gcc 3.41 and binutils 2.15.  As far as I know
only recently has this become a problem.

- Raw text -