(Thread / Exception) Stepping Forwards & Backwards
Allowing to step the execution of the application forwards, but also watching it back by stepping back through the collected history and emulating the application’s state at that point.
Stepping stops automatically if a specific step instruction is not reached within the specified timeout.
Thread stepping
You can also step specific threads, and please note that this does not cause this thread only to step. Every thread will keep stepping till this particular thread does.
If you are interested in only stepping a specific thread and keeping the other threads paused, see the thread only stepping roadmap item.
Exception stepping
You can also step within a collected exception, see the exception details view.
Step instructions
Step Into
Steps to the next execution step include a function call, return or tailcall.
Step Over
Keeps stepping until it returns to this function or leaves the current function, or more technical: When the number of calls is smaller or equal to the amount of return and tail calls. The non-technical explanation is correct for thread-specific stepping, but in other cases, since we are stepping on all threads, the technical explanation is more appropriate.
Step Out
Keeps stepping until the current function returns, or more technical: When calls are smaller than the amount of return and tail calls. The non-technical explanation is correct for thread-specific stepping, but in other cases, since we are stepping on all threads, the technical explanation is more appropriate.
Step back into
Steps to the previous recorded execution step include a function call, return or tail call.
Step back over
Keeps stepping back to previously recorded execution until it returns to this function or leaves the current function, or more technical: When the number of calls is smaller or equal to the amount of return and tail calls. The non-technical explanation is correct for thread-specific stepping, but in other cases, since we are stepping on all threads, the technical explanation is more appropriate.
Step back out
Keeps stepping back to previously recorded execution steps before the current function is called, or more technical: When the number of calls is smaller than the amount of return and tail calls. The non-technical explanation is correct for thread-specific stepping, but in other cases, since we are stepping on all threads, the technical explanation is more appropriate.
Views using this feature
- Realtime Call Tree Rendering
- Realtime Call Stack Rendering
- Realtime Grouped Call Stack Rendering
- Thread Detail View
- Process Menu
See Also:
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.