Re: mi-watch.exp fail, pls help

Daniel Jacobowitz <drowfalse.org> wrote on
2008-01-17 22:44:10:

> On Thu, Jan 17, 2008 at 11:57:33AM +0800, ligangsunnorth.com.cn wrote:
> > After setting watchpoint to C, it will be hit at
0x11e, and PC will be 

> > 0x120 at the time,
> > but GDB will execute a single step, after that, PC
will be 0x122, so 
> > source line will be 36 but not 
> > expected 35.
> > Anyone can tell me how to resolve this problem?
> 
> Check your target configuration.  GDB thinks you have
non-steppable
> watchpoints, but you actually have continuable
watchpoints.

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.

Dose it mean that my target can not match the action of
GDB?

> Daniel Jacobowitz
> CodeSourcery

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?

-- 
Daniel Jacobowitz
CodeSourcery