Re: mi-watch.exp fail, pls help

Daniel Jacobowitz <drowfalse.org> wrote on
2008-01-18 23:20:23:

> On Fri, Jan 18, 2008 at 12:25:43PM +0800, ligangsunnorth.com.cn wrote:
> > After a watchpoint trap in my target, the PC
points to the instruction 

> > after the one that caused the trap. 
> > But after stepping over the traped
instruction(example store), my 
target 
> > increases PC to the next instruction, so,
> > the source line will not be correct. It occurs at
whatever 
> > HAVE_NONSTEPPABLE_WATCHPOINT or
HAVE_CONTINUABLE_WATCHPOINT.
> 
> If you have continuable watchpoints, GDB should not
step after
> hitting a watchpoint.  The store has already happened
when the
> watchpoint triggers, right?

The store triggers the watchpoint, but it does not execute.

> -- 
> Daniel Jacobowitz
> CodeSourcery

On Mon, Jan 21, 2008 at 09:15:27AM +0800, ligangsunnorth.com.cn wrote:
> The store triggers the watchpoint, but it does not
execute.

GDB does not currently support watchpoints on any target
that requires
the debugger to decrement PC after the watchpoint triggers. 
You might
want to handle this in your debug stub, and pretend the PC
was before
the store.

-- 
Daniel Jacobowitz
CodeSourcery