I think I follow what you're saying.  You're suggesting a "per-session" breakpoint, basically.  Is that correct?

There is already an option to clear all breakpoints.  You could arrange if you wish to make this clear only the in-memory breakpoints but leave the saved one to reload next time.  In this case, I assume you'd then need separate functions, (i) to clear breakpoints, (ii) to delete all saved breakpoints

Alternatively, the existing clear all breakpoints function could both clear the in-memory ones and delete the saved ones.   If you preferred this functionality, you might not need much additional coding.
---
John

I hunted down the issue.  Basically I think the error was related to restarting the program.  When restarted, Simply Fortran would send all its breakpoint and watch assignments to the debugger again, creating a second set of identical breakpoints and watches.  When you removed a breakpoint, it would remove one of them, but a second one was still present at the same location.

The bug fix does two things.  First, it blocks resetting all breakpoints when the Restart option is clicked.  Second, it makes sure before setting a breakpoint or watch that they don't already exist.

The changes will be present in 2.7, which should be available early next week.

I'll have a look at why it's occurring.  I suspect there may be a mismatch in line number consistency (0-based versus 1-based).

I have observed this behaviour during a single debugging session.  I haven't checked to see whether it survives exiting then re-starting.
---
John