X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Authentication-Warning: mcomail01.maxtor.com: iscan owned process doing -bs
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Executable corruption with UPX v1.24 and v1.25
Date: Tue, 15 Nov 2005 19:20:37 -0700
Message-ID: <71078E41DDE3E541B024832F34BC3D0DA30816@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: AcXqVFURBLHPJ8vdRO6MRJzAfPqZAA==
From: "Schumacher, Gordon" <gordon_schumacher AT maxtor DOT com>
To: "DJGPP List \(E-mail\)" <djgpp AT delorie DOT com>
X-OriginalArrivalTime: 16 Nov 2005 02:20:37.0760 (UTC) FILETIME=[5534C000:01C5EA54]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jAG3CbxL024952

Just a heads-up to those out there using UPX to compress their
executables...

With the v1.25 release of UPX, if I build a particular executable (linked
with -s to strip debug symbols), and then compress and decompress
the generated executable, the finished product is 4KB smaller than the
original compiled program - and crashes in a way that the original does
not.

If I use version 1.93 beta of UPX, the file compares properly after
compression and decompression.

I've e-mailed the authors of UPX, and Markus Oberhumer has replied that
he recalls that v1.93 adds a workaround for a DJGPP linker bug.  I don't
have any more information than that - but I thought I'd give everyone out
there a warning so you're not tearing at your hair if your executable is
crashing inexplicably (especially if it's only the "release" build!)