From: iverson@cisco.com (Tim Iverson)
Subject: Debugging info for commercial linkers?
8 Aug 1997 02:24:27 -0700
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <199708080834.BAA01228.cygnus.gnu-win32@stars.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Original-To: gnu-win32@cygnus.com
X-Mailer: ELM [version 2.4 PL25]
Original-Sender: owner-gnu-win32@cygnus.com

I just noticed that my linker (PharLap) isn't picking up debugging
information from the GCC compiled objects.  I'm using -gcoff (obviously
stabs won't work).  According to objdump, the output file looks like it has
all the right debug stuff in it, but the linker is ignoring it.

Is coff debug format just too different from pe-i386?  I was under the
impression that the formats were almost identical.  Since the linker isn't
dying on the coff debug records, I suspect it isn't too different.  Anyone
wanna point me to a pe-i386 format reference so I can fix it?

Please don't tell me the -gcoff format is correct for pe-i386 debugging;
that would mean I'll have to add OMF support to BFD -- I'm stuck with the
linker.  ;-(

Thanks,


- Tim Iverson
  iverson@cisco.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".