Re: 1.7.25, Windows 7: dumper doesn't generate core file

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Mar 19 16:54, Sam Liapis@constrainttec.com wrote:
> 
> You're write Corrina I tried you're suggested test and it clearly
> proved ALL file sections are loaded.
> 
> I found a great memory visualiser tool VMMap here:
> http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx
> 
> I then re-run my original test and used VMMap to compare all DLL
> section addresses with dumper's diagnostic trace.
> 
> It turns out around half of the DLL section addresses didn't line-up
> with the sensible VMAs shown in VMMap's display.
> 
> For example the problematic *sechost.dll *file presented with the
> following differences:
> 
> DUMPER OUTPUT:
> ...
> got debug event 6
> excluding section: name=.text   base=*0x2b21000* size=00012c1b  <==
> NOTE the way out of range section VMA.
> added module *0x75510000* C:\Windows\SysWOW64\sechost.dll
> ...

Does dumper, by any chance, use the VMA address from the file, rather
than the real memory address when a DLL has been rebased by the Windows
loader?  If so, it's perhaps just another BFD function which has to be
called.

> At this stage I don't have time to dig into binutils source which
> appears to be providing the erroneous section VMAs.
> 
> I have to think about how I might present this back to the binutils
> mailing list given it's in a Windows environment.

Thanks a lot for looking into this anyway.  I'm looking forward to
your patches.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgp_26CQkP5Ni.pgp
Description: PGP signature