In the simplest case, breakpoints are locations where you wish the debugger to pause execution at so that you can examine your program's state at that point. Without breakpoints, you will not be able to precisely control the location of where the debugger should pause. Setting breakpoints is thus an essential debugging activity.
BugSeeker however is not limited to being able to set line breakpoints. You may set breakpoints by method name, by class and even set more powerful breakpoints that stop whenever certain exceptions are thrown or whenever a particular field is modified or accessed.
You also have the ability to assign conditions to breakpoints such as telling BugSeeker to pause the debug session only when certain conditions are met or only when a breakpoint is encounter a specific number of times.
Unlike their name, breakpoints do not necessarily have to pause a debug session. You can, for instance, create breakpoints that only evaluate expressions when encountered and display the results to the Console.
Breakpoints are stored with the current project. Changing the properties of a breakpoint affects all currently active debug sessions launched for that project.