bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/2768] readelf and segmented addresses in DWARF2/3 aranges


From: stephane dot chauveau at philips dot com
Subject: [Bug binutils/2768] readelf and segmented addresses in DWARF2/3 aranges
Date: 28 Jun 2006 10:01:28 -0000

------- Additional Comments From stephane dot chauveau at philips dot com  
2006-06-28 10:01 -------
I checked the pathc and it seems to work fine. 
The only remaining problem is the one I described in comment 8
The overall size when both the ponter and segment size are 4 bytes is 64 bit but
only 32bit are displayed. More generally, DWARF2 does not fully specify how to
interpret a segmented address so it would make sense to display each segemented
address (and the length too) as a byte sequence instead of converting it to a
numerical value. 

The current output for a_4_4.elf looks relatively good because the file is
little endian:  

    Address  Length
    000b0000 2
    00050000 9
    00000200 20
    00000214 536
    00000000 0

If the file was big endian (or if the relative order of the segment and offset
part of each address were swapped), the other 32 bit would be used and the
output would be:

    Address  Length
    00000001 0
    00000001 0
    00000000 0
    00000000 0
    00000000 0

The output obtained with printing the raw sequences of bytes would be: 
  
    Address            Length
    00000001000b0000 0x0000000000000002
    0000000100050000 0x0000000000000009
    0000000000000200 0x0000000000000014
    0000000000000214 0x0000000000000218
    0000000000000000 0x0000000000000000

I prefixed the length by '0x' to avoid a potential ambiguity because the it is
currently expressed in decimal for non segmented addresses.    

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2768

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

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