[Lldb-commits] [lldb] Add docs describing how the thread plan stack affects stepping (PR #110167)
Alex Langford via lldb-commits
lldb-commits at lists.llvm.org
Thu Sep 26 15:35:35 PDT 2024
================
@@ -536,6 +536,33 @@ This command will run the thread in the current frame until it reaches line 100
in this frame or stops if it leaves the current frame. This is a pretty close
equivalent to GDB's ``until`` command.
+One other useful thing to note about the lldb stepping commands is that they
+are implemented as a stack of interruptible operations. Until the operation -
+e.g. step to the next line - is completed, the operation will remain on the
+stack. If it is interrupted, new stepping commands will result in their
+operations being pushed onto the stack, each of them retired as they are completed.
+
+Suppose, for instance, you ``step-over`` a source line, and hit a breakpoint
+in a function called by the code of the line you are stepping over. Since the step-over
----------------
bulbazord wrote:
There's a lot of qualifiers in the second clause of the first sentence. I think you could rephrase it as something like this.
Suggestion:
```
Suppose, for instance, you `step-over` a source line with a function call. If there is a breakpoint placed in that function, LLDB will stop there with the `step-over` operation still on the stack.
```
https://github.com/llvm/llvm-project/pull/110167
More information about the lldb-commits
mailing list