This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: FYI: fix big-endian bug with DWARF_VALUE_STACK
- From: Tom Tromey <tromey at redhat dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 24 Feb 2010 09:30:35 -0700
- Subject: Re: FYI: fix big-endian bug with DWARF_VALUE_STACK
- References: <201002241411.o1OEBrHC011378@d12av02.megacenter.de.ibm.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> This seems somewhat different in that the DW_OP_implicit_value
Ulrich> explicitly provides data of a certain length. On the other
Ulrich> hand, DW_OP_stack_value refers to the value on top of the stack,
Ulrich> which -as I understand it- is a numerical value, not a sequence
Ulrich> of bytes of defined length.
Elements on the operand stack are explicitly address-sized. From DWARF
1.11.1:
Each element of the stack is the size of an address on the target
machine.
Ulrich> So it would seem to me that you should be able to request that
Ulrich> this value be represented in any arbitrary length ...
That interpretation makes sense to me, but so does the one making it an
error. I suspect we will never run across code that exercises this. If
you want to change it, I have no objection.
Tom