Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
From:	"Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To:	<kde-cygwin AT mail DOT kde DOT org>, "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>,
	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc:	"Binutils" <binutils AT sources DOT redhat DOT com>,
	"Cygwin-Apps" <cygwin-apps AT cygwin DOT com>
Subject:	RE: ordinal linking for cygwin ld
Date:	Sun, 28 Apr 2002 14:26:12 +0200
Message-ID:	<001e01c1eeaf$e27c02b0$d36707d5@BRAMSCHE>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To:	<001b01c1eeae$afa0b670$d36707d5@BRAMSCHE>
Importance:	Normal

> > Mostly. I'm a bit rusty - it's been a while since I grokked the
> > auto-import stuff. I'm getting back into it at the moment. The thing
> > that I don't follow at the moment is the how the linker fixup places the
> > exported data -variable- at a fixed rva at dll load time. The IAT is
> > -meant- to point straight to functions after the fixup occurs, so
> > pointing at an address in the .dll .text segment is fine.
                                  ^^^^
>
> Not into the dll, into the client code.

I was wrong. ... points to a data variable address located in the dll, which may
be in the .text or .data or .bss segment of the dll, but the patched address
lies in the clients .text segment.

- Raw text -