Add LLDB debugger support to swift-test command #9085
Draft
+1,209
−21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
plemarquand
force-pushed
the
swift-test-lldb-2
branch
from
41c3aa6 to
5a8044c
Compare
|
@swift-ci please test |
pmattos
approved these changes
Sep 2, 2025
pmattos
reviewed
Sep 2, 2025
| } | ||
|
|
||
| @Test(arguments: SupportedBuildSystemOnAllPlatforms) | ||
| func debuggerFlagWithBothTestingSuites(buildSystem: BuildSystemProvider.Kind) async throws { |
There was a problem hiding this comment.
question: Would there be an easy way to actually interact with LLDB during tests (eg,stdin)? For instance, send it some commands and check back the expected results? Maybe you did it already... and I missed it :)
There was a problem hiding this comment.
One of the reasons this is still in draft is I want to address that. I think I'd have to add supplemental commands to the file that gets passed to LLDB that contains its setup commands. That would let us set specific breakpoints in tests, though I still haven't figured out how to inspect the output since we replace the running process with execv.
pmattos
reviewed
Sep 2, 2025
plemarquand
force-pushed
the
swift-test-lldb-2
branch
from
a2b2ddf to
9954eb4
Compare
|
@swift-ci test |
Introduces interactive debugging capabilities to `swift test` via a `--debugger` flag enabling developers to failing tests directly within LLDB. This adds debugging parity with `swift run --debugger` which allows users to debug their executables directly. When launching lldb this implenentation uses `execv()` to replace the `swift-test` process with LLDB. This approach avoids process hierarchy complications and ensures LLDB has full terminal control for interactive debugging features. When there is only one type of tests the debugger creates a single LLDB target configured specifically for that framework. For XCTest, this means targeting the test bundle with xctest as the executable, while Swift Testing targets the test binary directly with appropriate command-line arguments. When both testing frameworks have tests available we create multiple LLDB targets within a single debugging session. A Python script automatically switches targets as the executable exits, which lets users debug both types of tests spread across two executables in the same session. The Python script also maintains breakpoint persistence across target switches, allowing you to set a breakpoint for either test type no matter the active target. Finally, we add a `failbreak` command alias that sets breakpoint(s) that break on test failure, allowing users to automatically stop on failed tests. Issue: swiftlang#8129
plemarquand
force-pushed
the
swift-test-lldb-2
branch
from
6cb6b72 to
d916038
Compare
plemarquand
force-pushed
the
swift-test-lldb-2
branch
from
d916038 to
d056ae8
Compare
|
@swift-ci test windows |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces interactive debugging capabilities to
swift testvia a--debuggerflag enabling developers to failing tests directly within LLDB.This adds debugging parity with
swift run --debuggerwhich allows users to debug their executables directly.When launching lldb this implenentation uses
execv()to replace theswift-testprocess with LLDB. This approach avoids process hierarchy complications and ensures LLDB has full terminal control for interactive debugging features.When there is only one type of tests the debugger creates a single LLDB target configured specifically for that framework. For XCTest, this means targeting the test bundle with xctest as the executable, while Swift Testing targets the test binary directly with appropriate command-line arguments.
When both testing frameworks have tests available we create multiple LLDB targets within a single debugging session. A Python script automatically switches targets as the executable exits, which lets users debug both types of tests spread across two executables in the same session. The Python script also maintains breakpoint persistence across target switches, allowing you to set a breakpoint for either test type no matter the active target.
Finally, we add a
failbreakcommand alias that sets breakpoint(s) that break on test failure, allowing users to automatically stop on failed tests.Issue: #8129