Skip to content

Conversation

@cachemeifyoucan
Copy link
Contributor

@cachemeifyoucan cachemeifyoucan commented Dec 15, 2025

  • Explanation: Cleanup some error diagnostics in ExplicitCASModuleLoader for LLDB's usage. This allows ExplicitCASModuleLoader to be used with other module loader as fallback without triggering an error when it failed to load.
  • Scope: This allows LLDB's new usage of ExplicitCASModuleLoader.
  • Issues: rdar://166490023
  • Original PRs: [CAS|LLDB] Cleanup diagnostics in ExplicitCASModuleLoader #86060
  • Risk: Low. Diagnostics Only.
  • Testing: Covered by LLDB tests.
  • Reviewers: @artemcm

While configuring LLDB to use ExplicitCASModuleLoader, it enounters some
error diagnostics that causes module loading to fail, rather than fall
back to the next module loader.

This commit clears:
* Allow ExplicitCASModuleLoader to be initialized with an empty explicit
  module map CASID
* Do not trigger error diagnostics when module lookup failed in module
  dependency scanner.

rdar://166490023
@cachemeifyoucan cachemeifyoucan requested a review from a team as a code owner December 15, 2025 18:01
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please test

@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please test windows platform

1 similar comment
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please test windows platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant