Re: [Lldb-commits] [PATCH] Report stopped by trace if none of the watchpoint was hit

On armv7 architecture systems, there are 4 hardware breakpoint registers (DBGBVR) and 4 hardware watchpoint registers (DBGWVR). The breakpoint registers track values in the pc register. You can also say stop when the PC is not equal to this value which is how single instruction stepping is

Re: [Lldb-commits] [PATCH] Report stopped by trace if none of the watchpoint was hit

It could be that the kernel reports a watchpoint hit on single stepping because on arm single stepping is actually implemented using hardware breakpoints. This is just a guess, but in any case it might be interesting to create a test case, which what happens with single stepping after we have

Re: [Lldb-commits] [PATCH] Report stopped by trace if none of the watchpoint was hit

Thanks for noticing this bug and for all of the suggestions. I created a new fix what address the actual root cause of the problem with reporting the right stop reason from lldb-server. For ARMv8 the watchpoint handling is not implemented yet, but it should be possible to implement the

Re: [Lldb-commits] [PATCH] Report stopped by trace if none of the watchpoint was hit

The approach looks right. I'll let somebody who works on the NativeThread side weigh in on whether the implementation is correct. http://reviews.llvm.org/D8081 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ ___