From:	iverson AT cisco DOT com (Tim Iverson)
Subject:	Re: Debugging info for commercial linkers?
8 Aug 1997 17:31:31 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199708082324.QAA08599.cygnus.gnu-win32@stars.cisco.com>
Mime-Version:	1.0
Original-To:	jazz AT softway DOT com
Original-Cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<33EB9018.7A66@softway.com> from "Jason Zions" at Aug 8, 97 03:31:04 pm
X-Mailer:	ELM [version 2.4 PL25]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Thanks!  This is incredibly helpful.  While it may not be the best news for
my application, it probably means that it would be quicker and surer for me
to just add OMF support (which is very well-documented) to BFD.

Is there some compelling reason folks are even trying to support pe-i386
given that MS seems uninterested in documenting it?  I guess if MSC outputs
it, that might be a tiny reason.  ;-)


- Tim


+----------------
| Date: Fri, 08 Aug 1997 15:31:04 -0600
| From: Jason Zions <jazz AT softway DOT com>
| To: Tim Iverson <iverson AT lionheart DOT com>
| CC: gnu-win32 AT cygnus DOT com
| Subject: Re: Debugging info for commercial linkers?
| References: <m0wwuFW-000SUZC AT lionheart DOT com>
| 
| Variables are completely hosed. Line numbers for functions are partly
....
| There isn't a *really* good reference for the NT PE format. Chunks of it
| are discussed in various MSDN articles; some of it can be derived from
| various public headers in the SDK. Some of it, though, requires heavy
| duty bit-grovelling detective work.
| 
| Jason
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -