Fix bit-/byte-offset mismatch in parameter to read_value_memory
authorAndreas Arnez <arnez@linux.vnet.ibm.com>
Tue, 13 Jun 2017 13:20:31 +0000 (15:20 +0200)
committerAndreas Arnez <arnez@linux.vnet.ibm.com>
Tue, 13 Jun 2017 13:20:31 +0000 (15:20 +0200)
commit23f945bf8cebf348154aff43782de2e1977e9230
treef4117bc4ecbce340ec673335ca084de240bdb969
parentf236533e3c6a2693bea879b2a4d24d1229864ac9
Fix bit-/byte-offset mismatch in parameter to read_value_memory

The function read_value_memory accepts a parameter embedded_offset and
expects it to represent the byte offset into the given value.  However,
the only invocation with a possibly non-zero embedded_offset happens in
read_pieced_value, where a bit offset is passed instead.

Adjust the implementation of read_value_memory to meet the caller's
expectation.  This implicitly fixes the invocation in read_pieced_value.

gdb/ChangeLog:

* valops.c (read_value_memory): Change embedded_offset to
represent a bit offset instead of a byte offset.
* value.h (read_value_memory): Adjust comment.
gdb/ChangeLog
gdb/valops.c
gdb/value.h
This page took 0.026817 seconds and 4 git commands to generate.