This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Strange reporting of symbol addresses for a Windows DLL

To: binutils at sources dot redhat dot com
Subject: Strange reporting of symbol addresses for a Windows DLL
From: Christopher Faylor <cgf at redhat dot com>
Date: Wed, 7 Feb 2001 23:50:06 -0500

I've noticed recently that when I do a

    i686-pc-cygwin-nm cygwin1.dll

the symbols that are reported look like this:

    c209e000 b .bss
    c209e000 b .bss
    c209e000 b .bss
    c209e010 b .bss
    c209e770 b .bss
    c209e790 b .bss
    c209e790 b .bss
    c209e790 b .bss
    c209e9b0 b .bss
    c209e9b0 b .bss

rather than this:

    6109e000 b .bss
    6109e000 b .bss
    6109e000 b .bss
    6109e010 b .bss
    6109e770 b .bss
    6109e790 b .bss
    6109e790 b .bss
    6109e790 b .bss
    6109e9b0 b .bss
    6109e9b0 b .bss

I know for a fact that all symbols in cygwin should be 610xxxxx since that is the base
that I set for the DLL.

Oddly enough 0xc2 = 0x61 + 0x61 .  Could this be a clue for what is wrong?

cgf

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]