diff options
author | Kevin Buettner <kevinb@redhat.com> | 2020-06-11 18:58:49 -0700 |
---|---|---|
committer | Kevin Buettner <kevinb@redhat.com> | 2020-07-22 12:42:31 -0700 |
commit | 5efb677960e786a7cfa3b5a53f15cc6656f33f02 (patch) | |
tree | f1aff157d20297eb39ed9c9679be06909f75a8df /gdb/arch-utils.c | |
parent | 94c265d790b88e691b9ea0173b7000a54a3eb0a0 (diff) | |
download | gdb-5efb677960e786a7cfa3b5a53f15cc6656f33f02.zip gdb-5efb677960e786a7cfa3b5a53f15cc6656f33f02.tar.gz gdb-5efb677960e786a7cfa3b5a53f15cc6656f33f02.tar.bz2 |
Update binary_get_section_contents to seek using section's file position
I have a patch for GDB which opens and reads from BFDs using the
"binary" target. However, for it to work, we need to be able to get a
section's contents based from the file position of that section.
At the moment, reading a section's contents will always read from the
start of the file regardless of where that section is located. While
this was fine for the original use of the "binary" target, it won't
work for my use case. This change shouldn't impact any existing
callers due to the fact that the single .data section is initialized
with a filepos of 0.
bfd/ChangeLog:
* binary.c (binary_get_section_contents): Seek using offset
from section's file position.
Diffstat (limited to 'gdb/arch-utils.c')
0 files changed, 0 insertions, 0 deletions