This is the mail archive of the binutils@sourceware.org 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]
Other format: [Raw text]

Re: [PATCH] objdump: Handle 32-bit base address in debug_ranges / debug_loc.


On Thu, Nov 26, 2015 at 11:26:20PM +0000, Andrew Burgess wrote:
> binutils/ChangeLog:
> 
> 	* dwarf.c (is_max_address): New function.
> 	(display_loc_list): Remove out of date comment, use
> 	is_max_address.
> 	(display_debug_ranges): Likewise.
> 
> binutils/testsuite/ChangeLog:
> 
> 	* binutils-all/objdump.exp: Add test for .debug_ranges decode.
> 	* binutils-all/dw2-ranges.S: New file.
> 	* binutils-all/dw2-ranges.W: New file.

OK, but..

> --- /dev/null
> +++ b/binutils/testsuite/binutils-all/dw2-ranges.W
> @@ -0,0 +1,11 @@
> +
> +.*:     file format .*
> +
> +Contents of the \.debug_ranges section:
> +
> +    Offset   Begin    End
> +    00000000 ffffffff 0000000(0|4) \(base address\)
> +    00000000 0000000(0|4) 0000000(4|8) 
> +    00000000 ffffffff 0000000(0|8) \(base address\)
> +    00000000 0000000(0|8) 0000000(4|c) 
> +    00000000 <End of list>

Why allow zero for the base address, and the variant ranges?

-- 
Alan Modra
Australia Development Lab, IBM


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