add_hw_breakpoint
called on every step
#77
-
Hi Daniel, I am wondering if maybe I'm did something wrong with my implementation: If I run a debug session where I set a HW breakpoint and then use If this is what I should expect, I guess the right approach here is then for me to just delete breakpoints every time I'm going to execute the gdb state machine and expect it to reconfigure everything for me (e.g., which pretty much means I don't have to keep any state about breakpoints in target) or maybe it's better to just check if the breakpoint is already installed for the given address and ignore the request (that would be fine as long as I can expect that Either way would for implementation, I am mainly just not sure if this is intended behavior of |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hey Gerd, If possible, could you please post a trace log of the GDB RSP packets? Incoming packets get logged via this
In the meantime... I believe the GDB Client will actually clear + reset breakpoint whenever it resumes the target, so the behavior you're seeing might be reasonable. Is |
Beta Was this translation helpful? Give feedback.
-
Hm sorry this is pretty embarrassing. I didn't realize I didn't have a log statement in |
Beta Was this translation helpful? Give feedback.
Hey Gerd,
If possible, could you please post a trace log of the GDB RSP packets? Incoming packets get logged via this
log::trace!
statement, and outgoing packets are logged via thislog::trace!
statement.In the meantime... I believe the GDB Client will actually clear + reset breakpoint whenever it resumes the target, so the behavior you're seeing might be reasonable. Is