Andes Workshop

Gdb command next and finish use "SW breakpoint" to implement it.

If you would like to use HW breakpoints to implement next and finish, you could use memory map in AndeSight to force it to set HW breakpoints.


---------------------
This is from gdb manual
http://sourceware.org/gdb/onlinedocs/gd ... reaks.html

For some targets, gdb can automatically decide if hardware or software breakpoints should be used, depending on whether the breakpoint address is read-only or read-write. This applies to breakpoints set with the break command as well as to internal breakpoints set by commands like next and finish. For breakpoints set with hbreak, gdb will always use hardware breakpoints.

You can control this automatic behaviour with the following commands::


set breakpoint auto-hw on
This is the default behavior. When gdb sets a breakpoint, it will try to use the target memory map to decide if software or hardware breakpoint must be used.
set breakpoint auto-hw off
This indicates gdb should not automatically select breakpoint type. If the target provides a memory map, gdb will warn when trying to set software breakpoint at a read-only address.