Enable HwbpManual #541
Enable HwbpManual #541
Conversation
lz-bro
force-pushed
the
enable_HwbpManual
branch
from
e880b5b
to
769f08a
Compare
| @@ -710,6 +715,7 @@ def test(self): | |||
| self.gdb.p("$pc") | |||
| assertRegex(output, r"[bB]reakpoint") | |||
| assertIn("rot13 ", output) | |||
| self.gdb.stepi() | |||
There was a problem hiding this comment.
why do we need this stepi ?
There was a problem hiding this comment.
riscv-tests/debug/programs/debug.c
Lines 65 to 68 in 7dfa49b
According to the program, I think that the breakpoint should be hit 2 times at rot13, and then hit at crc32a and _exit sequentially. So stepi avoids hitting the rot13 breakpoint at the same position as main
There was a problem hiding this comment.
So stepi avoids hitting the rot13 breakpoint at the same position as main
I don't get it. What do you mean "at the same position as main" ? main and rot13 should have different addresses. When gdb issues a continue request it issues a single-step and then issues a real continue. The breakpoint at main should not be hit.
debug/gdbserver.py
Outdated
| if value == tdata1: | ||
| value = self.gdb.p("$tdata1") | ||
| if value == tdata1 or \ | ||
| (value >> (xlen-4) == 0x6 and \ |
There was a problem hiding this comment.
value >> (xlen-4) == 0x6 What is the purpose of this condition? If I read this right we explicitly ask for TYPE=2 trigger. How come we end up with TYPE=6?
There was a problem hiding this comment.
The purpose is to be compatible with spec 1.0 and 0.13. On our hardware that supports spec 0.13, setting the TYPE to 2 trigger actually we end up with TYPE=6.
There was a problem hiding this comment.
can we instead just re-request type==6 if the resulting value of tdata1 is different? I believe this would enable us to support wide range of platforms in a more cleaner way.
Signed-off-by: 梁镇 <[email protected]> Change-Id: I2ee8718f03d6e381369b7d3bb0222563789ed525
Change-Id: I2ee8718f03d6e381369b7d3bb0222563789ed525