The next command steps one source line (stepping over calls).
The dbx step_events environment variable (see Setting dbx Environment 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 given signal while stepping.
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.
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 given, the deadlock avoidance measure of the generic next command is defeated.
See also nexti Command for machine-level stepping over calls.
For information on lightweight processes (LWPs), see the Solaris Multithreaded Programming Guide.
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 lwpid is given, the deadlock avoidance measure of the generic next command is defeated.
For information on lightweight processes (LWPs), see the Solaris Multithreaded Programming Guide. threaded Programming Guide.