MI: reporting of multiple breakpoints

[Eli Zaretskii]

> Date: Fri, 17 Feb 2006 15:01:50 -0500
> From: Paul Koning <pkoning@equallogic.com>
> Cc: ghost@cs.msu.su, gdb@sources.redhat.com
> 
> It is a bad thing for the break at x to fail due to the bad luck of
> having a watch exception at the preceding instruction.

I agree.  But the current code was written for a reason, I think, so
I'm curious to know what was that reason.

> If the two stops happened to be the SAME instruction, then you have
> plausible deniability.

Yes; except that if they happen on the same instruction, they are
still two different events: the breakpoint breaks _before_ the
instruction, the watchpoint _after_ it.  At least on x86.  So we can
announce both even in this case.