From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<9706151827.AA13357@clio.rice.edu>
Subject:	Re: Latest stub
To:	salvador AT inti DOT edu DOT ar (Salvador Eduardo Tropea)
Date:	Sun, 15 Jun 1997 13:27:59 -0600 (CDT)
Cc:	robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de, djgpp-workers AT delorie DOT com
In-Reply-To:	<m0wcVKT-000S1kC@ciati.edu.ar> from "Salvador Eduardo Tropea" at Jun 13, 97 03:38:25 pm

> Please Robert can you clarify why do you need to make fixed the size of the 
> stub? Is to simplify the code? can't you create a library function that:

The stub itself looks at the exe header it contains to determine where the
COFF image starts.  It's not hard (look at v2load) to handle any sized
stub if you are writing the code from scratch expecting it.  However, fixing
something like the binutils to do the right thing may be much harder 
and/or slower due to the way it's programmed.  

The DJP stub is an option which doesn't need to be used. It's there mostly for
backward compatibility and making it hard to debug the code - the best algorithm
uses the standard stub.

My 2 cents worth is to be happy the binutils handle the stub at all, and 
someone else is making the effort to do it :-)

Whoever does the work gets to decide how it behaves!

- Raw text -