This is the mail archive of the
mailing list for the Cygwin project.
Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/)
- To: Colin Peters <colin at bird dot fu dot is dot saga-u dot ac dot jp>
- Subject: Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/)
- From: Gunther Ebert <gunther dot ebert at ixos-leipzig dot de>
- Date: Mon, 24 Mar 1997 16:18:58 +0000
- Cc: gnu-win32 at cygnus dot com
- Organization: iXOS Anwendungs-Software GmbH
- References: <01BC386B.709FACA0@gbird0>
Colin Peters wrote:
> PS. Any confirmations on that statement about NT from other readers?
> Does stripping an executable make it work? Do you *have* to strip
> on NT? Is there a difference between the -s link option and using
> strip after linking?
My experiences with gnu-win32-produced binaries on NT 4.0 are:
- gcc -s is different from strip (strip produces a working binary
while gcc -s doesn't).
This statement isn't true for dlls or any binaries containing a
.reloc section. For binaries containing a .reloc section strip
doesn't work either.
- there is no need for stripping binaries which don't contain
- binaries containing resources have to be stripped to get them
working (NT 4.0 'feature')
they have to get a .reloc section
- gdb crashes when loading a gnu-win32-produced executable containing
a .reloc section (currently you cannot debug any programs containing
- gdb doesn't crash when loading any program containing a .reloc section
which isn't produced by gnu-win32 (in other words, you can load
notepad into gdb and it doesn't crash)
- dll relocation doesn't work in some cases, this problem is hard to
reproduce, it seems to apply to bigger dlls
I hope this helps to find the Bad Binary Bug.
iXOS Anwendungs-Software GmbH
Phone : +49 341 48503-0
Fax : +49 341 48503-99
www : http://www.ixos-leipzig.de
For help on using this list, send a message to
"firstname.lastname@example.org" with one line of text: "help".