X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID:	<3C25B25F.697A8992@is.elta.co.il>
Date:	Sun, 23 Dec 2001 12:30:55 +0200
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Mailer:	Mozilla 4.04 [en] (WinNT; I)
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: RFC - Dynamic loading
References:	<10112201703 DOT AA18384 AT clio DOT rice DOT edu>
Reply-To:	djgpp-workers AT delorie DOT com

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Thu, 20 Dec 2001 11:03:48 -0600 (CST)
> 
> > > Don't build it into a DXE until you've debugged it?
> > 
> > IMHO, that is not a very good alternative.  E.g., imagine a DLL 
> > written by someone else.
> 
> It would be similar today to debugging a stripped EXE image.

An analogy with stripped programs is not what I had in mind.  A
dynamic library can be distributed unstripped.  Since a dynamic
library eats up its disk space only once, it might actually make sense
not to strip it, since disk space is not a bug issue anymore.

> At this point it's probably worth while talking about what a DXE currently
> is.  You take a coff object file, strip the headers and replace the
> symbols/relocations with a pre-processed compressed fixup vector..
> 
> You could take the code inside DXEGEN and have it all done at runtime
> (for a much bigger loader footprint) using a coff format .o file.  If
> you wanted to retain symbols for debugging this is probably what you
> would need for GDB support.

How about making the debugging info a separate file?  Would that be
reasonable?  I think GDB could handle that.

- Raw text -