From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10210141330.AA25068@clio.rice.edu>
Subject: Re: CLIO 2.04 exe to use UPX in the next update
To: djgpp-workers AT delorie DOT com
Date: Mon, 14 Oct 2002 08:30:21 -0500 (CDT)
In-Reply-To: <200210140922.30663.pavenis@latnet.lv> from "Andris Pavenis" at Oct 14, 2002 09:22:30 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> UPX compressed DJGPP executables (built with last GCC versions) fails to run
> if uncompressed. 

Ouch.  But I think it's more likely that the problem is the new binutils?

A very interesting test would be:
 1) create a DJGPP image
 2) copy it away
 3) UPX it
 4) UPX decompress it
 5) compare
 6) What's changed?  Why different than previous?  

> version of UPX (1.23). I don't think it's so serious that I should reupload 
> binaries already compressed with UPX, but maybe we should not make a new ones
> before this is fixed.

I agree; you can't even run UPXed images in the debugger without 
decompressing.