dll base address

Christopher Faylor cgf@redhat.com
Sat Jun 9 21:40:00 GMT 2001


On Sat, Jun 09, 2001 at 11:16:51PM +1000, Robert Collins wrote:
>I haven't fixed the problem I reported with Paul Solovoskys patched ld,
>but I have a lead... it seems to be that cygwin1.dll is loaded after a
>dll that I was linking to, and that cygwin1.dll is getting relocated :
>
>(gdb) info dll
>DLL Name                               Load Address
>f:/src/ldt/auto-import-sample/dll.dll  610c1000
>e:/cygwin/bin/cygwin1.dll              02561000
>e:/winnt/system32/kernel32.dll         77e81000
>e:/winnt/system32/advapi32.dll         77db1000
>e:/winnt/system32/rpcrt4.dll           77d41000
>(gdb) print __cygwin_user_data
>Cannot access memory at address 0x610933a0
>
>As you can see, cygwin1.dll has been loaded at 02561000. It seems to me
>that if __cygwin_user_data is a non-relocatble variable, that we should
>mark cygwin1.dll as non-relocatable.
>
>Thoughts?

It's possible that this is just an artifact of faulty handling by gdb.
I'm not aware of any reason for cygwin1.dll to be unrelocatable.

If you look at the definition of __cygwin_user_data you'll see that
there is nothing magic about it.

Alternate theories is that there is either something wrong with gcc/binutils,
that we are missing something in the way that cygwin1.dll is linked, or
that there is something wrong with Paul's patched ld.

cgf



More information about the Cygwin-developers mailing list