Deactivated Breakpoints

Breakpoints that are deactivated will have their icons appear as a crossed hollow circle. Breakpoints are deactivated if they are invalid because BugSeeker is unable to set the breakpoint when a debug session first starts or when a debug session is currently active. There are many reasons as to why a breakpoint is invalid. Line breakpoints are invalid if the line specified does not contain any executable code; method breakpoints are invalid if the method we are to set a breakpoint for does not exist in the specified class; field watchpoints are invalid if the field we are to set a watchpoint for does not exist.

The only current way to check if a breakpoint has been deactivated or not is to open the Breakpoints dialog (View | Breakpoints) and examine the breakpoint's icon to see if it is deactivated. When you hover the mouse over a deactivated breakpoint, a message may be displayed explaining why the breakpoint could not be set.

Deactivated breakpoints are specific only to a given debug session. It may be possible for a breakpoint to be deactivated in one session while appearing active in another session of the same project, most likely because the sessions are using different Java runtimes. Thus, if you see that a breakpoint is deactivated, it applies only to the currently active session. Breakpoints will never appear deactivate if there are no active sessions.