gdb/760: Fix watchpoints when stepping over a breakpoint

[ac131313 at redhat dot com]

>Number:         760
>Category:       gdb
>Synopsis:       Fix watchpoints when stepping over a breakpoint
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 27 16:58:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
See:
http://sources.redhat.com/ml/gdb-patches/2002-04/msg00043.html

Reservations were expressed over the ``ad hoc'' nature of the solution.

--

DanielJ writes:

For some of the history of this problem, see PR gdb/81 and:
  http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html

How Peter's or Jim's patches worked for them, I'm not entirely sure; I
suspect there's been a change to shared library debugging since then, and/or
a severe deficiency in the testsuite somewhere.  When I tried it I got stuck
on the bp_shlib_event breakpoint.  We would hit it, remove, single-step
(trap expected), check where we were... and find ourselves at the
shared library breakpoint again because of DECR_PC_AFTER_BREAK!

Instead, I now collect only non-breakpoint events.  This appears to work
fine.  It causes no changes in the testsuite; a trivial followup patch to
update the formatting in annota2.exp fixes the test in question.  Is this OK
to commit?  Anyone see a problem with my method?

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: