Hello, it'd be good to know what are the steps to reproduce this situation from scratch. If you could recall what did you do before the breakpoints disappeared from the Breakpoints window, it'd help. The breakpoints can be deleted from file: <NB user dir>/config/Services/org-netbeans-modules-debugger-Settings.properties The file contains breakpoints, watches, windows columns of debugging windows, etc. It's debugger-specific. If you have nothing important there, delete the whole file. Or set just debugger.breakpoints.jpda.length property to 0 and NetBeans will read no breakpoints. It's important to close NetBeans first, then do the changes in the file (or delete it) and then start NetBeans.
Regards, Martin ________________________________ From: Peter Blemel <[email protected]> Sent: Monday, October 3, 2022 20:14 To: [email protected] <[email protected]> Subject: [External] : NetBeans 15 losing track of Java debugger breakpoints Hi Everyone, When debugging my NetBeans platform App, NetBeans 15 is submitting breakpoints to the debugger and my program stops on them. My issue is that I can't delete/disable them from Window -> Debugging -> Breakpoints because the list is empty. I have to let NB15 submit each breakpoint, click on the link in the Debugger Console (or hit the breakpoint at runtime) and clear them manually from in the source window. That is a workaround for LineBreakpoints. However, one of the breakpoints is a FieldBeakpoint, which can't be cleared from inside of the editor window (or at least I can't see how to do it). When a FieldBreakpoint is submitted, unlike a LineBreakpoint, there is no link to it in the Debugger Console window. When the debugger stops on this breakpoint, I can't remove it from the source window so it appears to be permanent. The result is that my program stops every time this variable is modified, and I can't find a way to delete the breakpoint. Where are Breakpoints persisted? Is there a text file that I can edit to manually remove them before starting the IDE? I don't know how it happened, or even if I can reproduce this behavior for a bug report. If I can figure it out, I'll submit an issue. Has anyone else seen this behavior? Thanks, peter
