Date: Fri, 13 Jun 1997 12:24:30 +0200 (METDST)
From: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
To: Oberhumer Markus <k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at>
Cc: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
        DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Latest stub
In-Reply-To: <199706122222.SAA17954@delorie.com>
Message-Id: <Pine.HPP.3.95q.970613121535.4046A-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Fri, 13 Jun 1997, Oberhumer Markus wrote:

> DJP comes with an option ('-s') to put the decompression code into the stub -
> in this case it will be 2560 bytes long.
> 
> The PMODE stub is > 10kB and I remember having seen some other stubs
> (DLM ?) that are even longer.

Ok. But I do you handle such files with any of the binutils?
Most common usage of the binutils are the programs for executables
objcopy, objdump, strip and ld. Where ld only creates executables
and the others are able to read them also. And also gdb have to
read executables.
But in your mentioned cases these are all situations where normally
not to run the binutils on the exe. Compressed DJGP exe's cannot be
handled by the binutils at all also without the fixed stub length.

And for the other cases I cannot say so much, because I don't use
them, but in these cases you should use unstubbed COFF images
when using the binutils and prepend the stub only when needed or
do a exe2coff on the program, run the binutils and then prepend
the stub again.

Robert