What are the benefits to the Step Over Thread and Step Into Thread teams?

Question

Can someone explain what the purpose of the Step Over Thread command and debugging is in the debugger in Xcode? In which case is it useful to use them, rather than the usual step and step? What is the difference and when does it matter?

Edit: To clarify the question, I am not asking about the difference between Step Over / Step Into / Step Out, I am asking about the difference between normal and "Thread" versions, and in which case one version is more useful than the other.

Answer 1

• Step in

Executes the current statement, and then stops in the following expression. If the current statement is a function or script call, then the debugger goes into that function or script, otherwise it stops in the following expression.

• Step forward

Executes the current statement, and then stops in the following expression. If the current statement is a function or script call, then the debugger executes the entire function or script, and it stops in the next statement after the function call.

• Step

Exits the current function and one level if the function is nested. If in the main body, the script is executed to the end or to the next breakpoint. Missed statements are fulfilled but failed.

The argument is generally about debugging, so take a look

What is the difference between Step Into and Step Over in the Eclipse debugger?

When looking at a specific focus, there is a thread, so you can look at your multi-threaded application as a single-threaded application without using multiple events / threads, etc., while you stop at a breakpoint. You have "stable maturity."

http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/060-Debug_Your_App/debug_app.html

Answer 2

I am just struggling with the same question. The question is a bit old, but it looks like I found the right answer.

Here in the documentation , I found something like this:

Control-Shift to enter the active stream or above it only when other flows stop (step icons show a dashed line, not a solid line under the arrow).

Control-Shift- <Fx Key or press> are appropriate shortcuts for thread versions in increments and steps forward. Thus, it seems that this only executes the current thread and pauses the temporary all other threads. Normal versions continue to execute all non-paused threads.

Answer 3

A very simple explanation of this term:

Step, steps, steps (debug menu)

Answer 4

According to this book :

Step over a thread and Step into a stream freeze all other threads while you push the thread you are debugging. Hold Shift and Control while pressing buttons or selecting commands in Debug to get the effect.