Sorry I was referring to hardware watchpoints when making this comment.

The breakpoint.c kludge I did as far as I remember is probably unwanted, I
just found that the
hardware breakpoints in 4-18 were in absolutely terrible shape staying in
when not wanted &
disappearing for no reason, has this code improved ?, my clueless kludge
improved the situation a tiny
bit in the test cases I was playing with.
I haven't had a chance to see whether the 5.0 code has improved
substantially in my opinion
this code needs a lot of attention by someone who knows it, if this code
has improved recently
please leave this out.

D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen