next

The next command with no arguments steps one line stepping over calls:

---

next

---

To step n lines skipping over calls:

---

next n

---

To deliver the given signal while executing the next command:

---

next ... -sig sig

---

The dbxenv variable step_events controls whether breakpoints are enabled during a step.

To step the given thread:

---

next tid

---

To step the given LWP (lightweight process):

---

next lwpid

---

This will not implicitly resume all LWPs when skipping a function. When an explicit tid or lwpid is given, the deadlock avoidance measure of the generic next is defeated.

With multithreaded programs, when a function call is skipped over, all LWPs are implicitly resumed for the duration of that function call in order to avoid deadlock. Non-active threads cannot be stepped.

---

Note -

For information on lightweight processes (LWPs), see the Solaris Multithreaded Programming Guide.

---