aboutsummaryrefslogtreecommitdiff
path: root/elfcpp
diff options
context:
space:
mode:
authorUlrich Weigand <ulrich.weigand@de.ibm.com>2014-09-17 17:29:27 +0200
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2014-09-17 17:29:27 +0200
commit5e43d46791c4c66fd83947a12d4f716b561a9103 (patch)
tree30db0542599d064756d8ebb4d758fc1decde26ef /elfcpp
parent2569ceb0b02cc5569af5f946d89b578510ac5ea1 (diff)
downloadgdb-5e43d46791c4c66fd83947a12d4f716b561a9103.zip
gdb-5e43d46791c4c66fd83947a12d4f716b561a9103.tar.gz
gdb-5e43d46791c4c66fd83947a12d4f716b561a9103.tar.bz2
PR gdb/17384: Do not print memory errors in safe_read_memory_integer
If accessing memory via safe_read_memory_integer fails, that function used to print an error message even though callers were perfectly able to handle (and even expected!) failures. This patch removes the confusing message by changing the routine to directly use target_read_memory. gdb/ChangeLog: PR gdb/17384 * corefile.c (struct captured_read_memory_integer_arguments): Remove. (do_captured_read_memory_integer): Remove. (safe_read_memory_integer): Use target_read_memory directly instead of catching errors in do_captured_read_memory_integer.
Diffstat (limited to 'elfcpp')
0 files changed, 0 insertions, 0 deletions