The next command steps one source line (stepping over calls).
The dbx step_events environment variable (see Setting dbxenv Variables) controls whether breakpoints are enabled during a step.
Step one line (step over calls). With multithreaded programs when a function call is stepped over, all LWPs (lightweight processes) are implicitly resumed for the duration of that function call in order to avoid deadlock. Non-active threads cannot be stepped.
Step n lines (step over calls).
Deliver the specified signal while stepping.
Step the specified thread.
Step the given LWP. Will not implicitly resume all LWPs when stepping over a function.
where:
n is the number of lines to step.
signal is the name of a signal.
thread-ID is a thread ID.
lwp-ID is an LWP ID.
When an explicit thread-id or lwp-ID is included, the deadlock avoidance measure of the generic next command is defeated.
See also nexti Command for machine-level stepping over calls.
Step one line (step over calls). With multithreaded programs when a function call is stepped over, all LWPs (lightweight processes) are implicitly resumed for the duration of that function call in order to avoid deadlock. Non-active threads cannot be stepped.
Step n lines (step over calls).
Step the given thread.
Step the given LWP. Will not implicitly resume all LWPs when stepping over a function.
where:
n is the number of lines to step.
thread-ID is a thread identifier.
lwp-ID is an LWP identifier.
When an explicit thread-ID or lwp-ID is included, the deadlock avoidance measure of the generic next command is defeated.