summaryrefslogtreecommitdiff
path: root/bfd/cpu-mep.c
diff options
context:
space:
mode:
authorPitchumani Sivanupandi <pitchumani.s@atmel.com>2015-10-06 18:29:03 +0200
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2015-10-06 18:29:03 +0200
commitcbd641edf3323ce354c0bc7eb54496057040b564 (patch)
tree0ae1f86b69551a1de4f69d8b4df53e4323f2a0db /bfd/cpu-mep.c
parent6540205329fe12999006bd886402823f4fce1c6e (diff)
downloadbinutils-gdb-cbd641edf3323ce354c0bc7eb54496057040b564.tar.gz
parse load_offset (bias) of restore command as long
Following failures are noticed for avr-gdb. This may be the case for targets like AVR which has integer_to_address hook defined. FAIL: gdb.base/dump.exp: struct copy, srec; value restored ok FAIL: gdb.base/dump.exp: struct copy, ihex; value restored ok FAIL: gdb.base/dump.exp: struct copy, tekhex; value restored ok These tests are failed because load_offset(bias) of restore command parsed as address. command: restore filename [binary] bias start end Except binary, other BFDs have a built-in location; gdb restores content at offset 'bias' from that location. So, 'bias' of 'restore' command should be parsed as address only when the file is binary. Below patch changes gdb to parse 'bias' as long if the file is not binary. gdb/ChangeLog 2015-10-06 Pitchumani Sivanupandi <pitchumani.s@atmel.com> * cli/cli-dump.c (restore_command): Parse load_offset (bias) as address only when the file is binary.
Diffstat (limited to 'bfd/cpu-mep.c')
0 files changed, 0 insertions, 0 deletions