bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should mem sections have overlapping addresses?


From: Sam address@hidden
Subject: Re: Should mem sections have overlapping addresses?
Date: Tue, 18 Mar 2014 09:54:47 +1100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0


I very much appreciate your response Alan.

This is very helpful and explains why Cygwin dumper gets in a bind as it
assumes all CODE & DEBUGGING flagged sections are in memory.

Thanks again,
Sam


On 16/03/14 20:40, Alan Modra wrote:
On Fri, Mar 14, 2014 at 11:15:38AM +1100, Sam Liapis at constrainttec dot com 
wrote:
$ objdump -h airdac_.exe
airpac_.exe:     file format pei-i386
Sections:
Idx Name          Size      VMA       LMA       File off  Algn
   0 .text         008d8980  00401000  00401000  00000400  2**4
                   CONTENTS, ALLOC, LOAD, READONLY, CODE, DATA
   ...
   7 .debug_info   151e2063  028ca000  028ca000  024b3000  2**0 <== VMA and 
SIZE match-up with trace above
                   CONTENTS, READONLY, DEBUGGING
As you can see from the flags above, .debug_info is not ALLOC, LOAD.
This means the section is not loaded into memory and the VMA is
irrelevant.  Another DLL could well occupy this space, because
airpac_.exe does not use that memory.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]