Skip to content

Commit d2cab32

Browse files
authored
update: clarify LLDB breakpoint behavior with Mojo JIT compilation (#229)
1 parent f410b78 commit d2cab32

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

book/src/puzzle_09/essentials.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -343,7 +343,18 @@ Output:
343343
Breakpoint 1: where = mojo`main, address = 0x00000000027d7530
344344
```
345345

346-
The debugger found your main function and will pause execution there.
346+
Or it may look like:
347+
348+
```
349+
Breakpoint 1: no locations (pending).
350+
WARNING: Unable to resolve breakpoint to any actual locations.
351+
```
352+
353+
If the breakpoint appears as pending, this is expected. Mojo programs are JIT-compiled, which means the debugger may not be able to resolve symbols until the program begins execution. In this case the breakpoint is registered, but LLDB cannot yet bind it to a concrete instruction address.
354+
355+
Once execution starts and the module is compiled, LLDB resolves the breakpoint automatically.
356+
357+
In either case the breakpoint has been set successfully and execution will pause there once the program runs.
347358

348359
**Step 2: Start your program**
349360

0 commit comments

Comments
 (0)