Skip to content

update: clarify LLDB breakpoint behavior with Mojo JIT compilation #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Bakobiibizo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update: clarify LLDB breakpoint behavior with Mojo JIT compilation #229

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion book/src/puzzle_09/essentials.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,7 +343,18 @@ Output:
Breakpoint 1: where = mojo`main, address = 0x00000000027d7530
```

The debugger found your main function and will pause execution there.
Or it may look like:

```
Breakpoint 1: no locations (pending).
WARNING: Unable to resolve breakpoint to any actual locations.
```

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.

Once execution starts and the module is compiled, LLDB resolves the breakpoint automatically.

In either case the breakpoint has been set successfully and execution will pause there once the program runs.

**Step 2: Start your program**

Expand Down