Internal breakpoints do not need IDs and assigning them from a counter separate from the user ID counter can be a cause of confusion. If a user breakpoint is overlayed on top of a pre-existing internal breakpoint the temporary ID will be surfaced as if it was a user ID, possibly conflicting with another user ID. If a temporary breakpoint is overlayed on top of a pre-existing user breakpoint and the user breakpoint is first deleted and then re-created, the user ID will be resurrected along with the breakpoint, instead of allocating a fresh one. This change removes internal breakpoint IDs entirely, only user breakpoints receive an ID. |
||
|---|---|---|
| .. | ||
| gdbserver_conn.go | ||
| gdbserver_unix.go | ||
| gdbserver_windows.go | ||
| gdbserver.go | ||
| rr_test.go | ||
| rr.go | ||