Skip to content

[docs] Add some information to DebuggingTheCompiler.md about working with the various simulators. #85590

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

Merged
merged 1 commit into from
Nov 19, 2025
+10 −0
Merged

[docs] Add some information to DebuggingTheCompiler.md about working with the various simulators. #85590

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
10 changes: 10 additions & 0 deletions docs/DebuggingTheCompiler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@ benefit of all Swift developers.
- [Viewing allocation history, references, and page-level info](#viewing-allocation-history-references-and-page-level-info)
- [Printing memory contents](#printing-memory-contents)
- [Windows Error Codes](#windows-error-codes)
- [Debugging Simulator Apps](#working-simulator-apps)
- [Debugging LLDB failures](#debugging-lldb-failures)
- ["Types" Log](#types-log)
- ["Expression" Log](#expression-log)
Expand Down Expand Up @@ -1201,6 +1202,15 @@ Some relevant Microsoft documentation:
* https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/0642cb2f-2075-4469-918c-4441e69c548a
* https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

## Debugging Simulator Apps

Sometimes one has to debug apps compiled for one of the simulators (e.x.: iOS
simulator). To manipulate the simulator from the command line, one uses the tool
called `simctl`. This lets one perform actions such as installing apps,
uninstalling apps, and of course launching apps. To pass through environment
variables to launched apps, one sets them in the calling environment using the
environment variable prefix `SIMCTL_CHILD_$ACTUAL_ENV_VAR_NAME`.

# Debugging LLDB failures

Sometimes one needs to be able to while debugging actually debug LLDB and its
Expand Down