delorie.com/archives/browse.cgi | search |
Message-Id: | <9607311844.AA21840@gnu.mc.xerox.com> |
To: | sandmann AT clio DOT rice DOT edu (Charles Sandmann) |
Cc: | djgpp-workers AT delorie DOT com (DJGPP developers) |
Subject: | Re: should stubify strip? |
In-Reply-To: | Your message of "Wed, 31 Jul 1996 08:22:01 PDT." |
<9607311422 DOT AA17908 AT clio DOT rice DOT edu> | |
Mime-Version: | 1.0 |
Date: | Wed, 31 Jul 1996 11:44:19 PDT |
From: | "Marty Leisner" <leisner AT sdsp DOT mc DOT xerox DOT com> |
> > It's acceptable for stubify to *always* strip the .exe. > > If you are a gdb user this makes sense, since gdb can't read symbols on the > end of a .EXE - but EDEBUG32 and FSDB can (but it might be argued that > for consistency only COFF files should keep them). It seem the first > step is to make a switch for stubify which could strip - then that could > optionally be part of the specs file. I don't have any strong options > on if stripping .EXEs should be default, but it would make a lot of > hello_world_size_inquiries disappear. But then you will get the > I don't get symbols when debugging inquiries ... Isn't there a program to go from .exe to coff? (exe2coff?) .exe's should not be stripped by default. -- marty leisner AT sdsp DOT mc DOT xerox DOT com Member of the League for Programming Freedom
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |