Step Commands

Stepping over your source code allows you to examine your program's state at each step in hopes of being able to pinpoint the exact location where the bug is. BugSeeker supports four kinds of step commands: stepping into methods, stepping without going into methods, stepping out of methods, and stepping into methods but skipping certain classes. All four stepping methods resume execution of all threads temporarily (even threads manually marked not-executable) so it is possible during the course of stepping that some other breakpoint event will be handled instead.