gdb/riscv: fix creating breakpoints at invalid addresses
authorChangbin Du <changbin.du@gmail.com>
Thu, 25 Mar 2021 11:02:23 +0000 (11:02 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 25 Mar 2021 11:10:02 +0000 (11:10 +0000)
commitd3cbca38dfdd29d919a74d72d7c4608864c68f63
treee32b5bbb3f66e9ff8ab313d6fcfc8f66900922ba
parentefa30ac3c504d24c55733a627abe49bd0368cf67
gdb/riscv: fix creating breakpoints at invalid addresses

To allow breakpoints to be created at invalid addresses,
target_read_code is used instead of read_code.  This was fixed in
commit:

  commit c01660c625766e848195285cc20581b9ed7ecfe2
  Date:   Wed Apr 17 00:31:43 2019 +0100

      gdb/riscv: Allow breakpoints to be created at invalid addresses

Unfortunately, the call to read_code was left in by mistake.  The
result is that GDB will fail when trying to create the breakpoint,
rather than when trying to install the breakpoint (as is the case with
other targets).

This commit fixes this mistake and removes the offending call to
read_code.

gdb/ChangeLog:

* riscv-tdep.c (riscv_breakpoint_kind_from_pc): Remove call to
read_code.
gdb/ChangeLog
gdb/riscv-tdep.c