You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple Swift version 3.0 (swiftlang-800.0.46.2 clang-800.0.38)
Target: x86_64-apple-macosx10.9
Additional Detail from JIRA
Votes
1
Component/s
LLDB for Swift
Labels
Bug
Assignee
None
Priority
Medium
md5: 4e80e0f98f6325462d3732d4035ae6d8
relates to:
SR-3169 lldb stops working when C module includes a header outside of module's include/ dir
Issue Description:
When a Clang module (CModule) is imported into Swift code (module Foo), that is then used by C code. LLDB is able to find Foo in dSYM, but fails to import the CModule module.
If you run build.sh in the attached sample, you will see:
warning: Swift error in module main.
Debug info from this module will be unavailable in the debugger.
error: in auto-import:
failed to get module 'Foo' from AST context:
error: missing required module 'CModule'
dmishe (JIRA User), hmm not sure. Have you tried this with a macOS package that includes the fix that went in SR-2637? Do you get the same behavior? The swift-lldb master branch is now quite a bit ahead of the swift 3.0 release's corresponding LLDB, and includes the SR-2637 change, so there is certainly potential for lookups to be handled differently given all the changes that came in from LLVM.org LLDB.
@trfiala what is the canonical way for LLDB to discover and load Clang modules? I would like to debug this issue some more and some pointers would be really helpful.
Attachment: Download
Environment
Apple Swift version 3.0 (swiftlang-800.0.46.2 clang-800.0.38)
Target: x86_64-apple-macosx10.9
Additional Detail from JIRA
md5: 4e80e0f98f6325462d3732d4035ae6d8
relates to:
Issue Description:
When a Clang module (
CModule
) is imported into Swift code (moduleFoo
), that is then used by C code. LLDB is able to find Foo in dSYM, but fails to import the CModule module.If you run build.sh in the attached sample, you will see:
The program itself runs just fine:
Clearly I am not telling the compiler enough for it to be able to reconstruct the context afterwards. But I am not sure what is missing.
The text was updated successfully, but these errors were encountered: