Error clearing stack watchpoint

[emilykmarx]

1. What version of Delve are you using (dlv version)? Backend=rr (5.7.0), on the recent commit with fixes for rr 5.7.0 (https://github.com/go-delve/delve/commit/7c7265f4e68a333bb084217e7b7ae065024e428b)

   Delve Debugger
   Version: 1.22.1
   Build: $Id: 0c3470054da6feac5f6dcf3e3e5144a64f7a9a48 $

2. What version of Go are you using? (go version)? go1.20.1 linux/amd64
3. What operating system and processor architecture are you using? Ubuntu 20.04 LTS, amd64

I’m noticing stack watchpoints aren’t cleared the way I’d expect. The CLI session and the target file are in this gist: https://gist.github.com/emilykmarx/c9bb39fdefd2ac8cfb843d53e867a12d, but as a summary:

• I set write watchpoints on the first four elements of a stack array
• The watchpoints hit as expected
• Continuing after the last hit, the watchpoints should all go out of scope
• But an error appears when it tries to clear one of them (index 3, address 0xc000051f28): could not clear out-of-scope watchpoint
• Also, the went out of scope and was cleared message appears twice for index 3, and does not appear for index 1 (0xc000051f18)
• The watchpoint at index 1 seems to stick around: Continuing once more, the target exits and it is still there (but with a nil address). After restart, it hits a few times in runtime functions – continuing past those, it eventually clears.

[emilykmarx]

I tried the same thing with the native backend (added CLI session for that to the gist) -- same issues with could not clear out-of-scope watchpoint and went out of scope and was cleared, with a few differences (the expected hit for index 3 doesn't happen, and restart gives breakpoint 3 can not be enabled for index 1)

[emilykmarx]

Thanks for fixing!