From: "Jan Beulich" <JBeulich@novell.com>
To: <me@cgf.cx>
Cc: <u-thiel@gmx.net>,<nickc@redhat.com>, <binutils@sources.redhat.com>
Subject: Re: PE32+ Format!
Date: Tue, 12 Apr 2005 06:42:00 -0000 [thread overview]
Message-ID: <s25b7bc7.014@emea1-mh.id2.novell.com> (raw)
>>> Christopher Faylor <me@cgf.cx> 11.04.05 19:37:32 >>>
>On Mon, Apr 11, 2005 at 06:04:37PM +0200, Jan Beulich wrote:
>>>By the way - is there any public documentation on the PE32+ format
>>>available ?
>>
>>I know only of the MSDN doc (which can't really be considered public I
>>guess), but since Cygwin appears to know about the (or at least some,
>>did a brief check only) 64-bit extensions they must have gotten them
>>from somewhere...
>
>? What 64-bit extensions does cygwin know about?
Just grep Cygwin's winnt.h for 'IMAGE.*64', and most of the hits will give you an idea; as I see one of the odd things is that they have quite a number of the structure changes, but they're lacking the change to the NT header (IMAGE_OPTIONAL_HEADER64) and the new 'magic' value to indicate its use. PE32+ isn't really a different format except for some slightly changed sub-structures to accomodate 64-bit values where needed (which I guess is why they don't call it PE64).
Jan
next reply other threads:[~2005-04-12 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 6:42 Jan Beulich [this message]
2005-04-12 13:46 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 17:50 Ulrich Thiel
2005-04-11 16:04 Jan Beulich
2005-04-11 17:37 ` Christopher Faylor
2005-04-08 16:40 Ulrich Thiel
2005-04-11 15:55 ` Nick Clifton
2005-04-11 20:56 ` Aaron W. LaFramboise
2005-04-12 7:33 ` Ulrich Thiel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s25b7bc7.014@emea1-mh.id2.novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=me@cgf.cx \
--cc=nickc@redhat.com \
--cc=u-thiel@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).