Skip to content

Add logging getLLDBLibPath to better diagnose failures#1943

Open
plemarquand wants to merge 2 commits intoswiftlang:mainfrom
plemarquand:get-lldb-lib-path-error-logging
Open

Add logging getLLDBLibPath to better diagnose failures#1943
plemarquand wants to merge 2 commits intoswiftlang:mainfrom
plemarquand:get-lldb-lib-path-error-logging

Conversation

@plemarquand
Copy link
Copy Markdown
Contributor

This will help diagnose the failure to find LLDB on Windows 6.2

Tasks

  • Required tests have been written
  • Documentation has been updated
  • Added an entry to CHANGELOG.md if applicable

@award999
Copy link
Copy Markdown
Contributor

Some suggestions of how we could taker debug logging even further

@plemarquand plemarquand force-pushed the get-lldb-lib-path-error-logging branch from 20bc398 to e06c829 Compare January 19, 2026 15:21
@plemarquand plemarquand added the full-test-run Perform a full test suite run. Apply this label before pushing up a PR or commit label Jan 28, 2026
@plemarquand plemarquand force-pushed the get-lldb-lib-path-error-logging branch from e06c829 to 24732d6 Compare January 28, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-test-run Perform a full test suite run. Apply this label before pushing up a PR or commit

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants