This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI: reporting of multiple breakpoints
> Date: Sun, 19 Feb 2006 13:13:13 -0500
> From: Paul Koning <pkoning@equallogic.com>
> Cc: drow@false.org, ghost@cs.msu.su, gdb@sources.redhat.com
>
> Yes, it is likely that the exception PC for a watchpoint exception
> points after the store, not at it.
No, the PC for the inferior's current address points after the store.
The PC for whatever instruction caused the watchpoint exception points
at that instruction. We are talking about 2 different values of PC.
> The issue is: what user watch/break is reported, and what line is
> reported?
We report the right watch and the right line. What we fail to do is
run the commands of the breakpoint whose location is the instruction
right after the one which caused the watchpoint exception. We need to
run those commands even if we decide not to announce the breakpoint.
> My argument is: if the hardware permits you to know the PC of the
> store, then you can do a BETTER job helping the user, by translating
> the address of the store, NOT the exception PC, back into a line
> number.
We already do this. In fact, we did this from day one of watchpoint
support. And we do this on all platforms that support watchpoints.