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
We recently hit an error where we passed an invalid module to -add_ast_path, this was completely our fault but it was a bit harder to debug because of the generic messages from LLDB. In the console once we stopped at a breakpoint you see:
path/to/binary: Cannot load Swift type information; AST validation error: The serialized module is corrupted.AST validation error: The serialized module is corrupted.
LOG_PRINTF(LIBLLDB_LOG_TYPES, "failed to parse AST section %zu of %zu.",
It would be great if the path to the invalid module was produced in one or both of these logs so that it would be some extra info to help debug. I was able to correlate the ordering of the logs from the types log with the output of `dsymutil -s binary | grep AST` to find the invalid module.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 775ec51e2004785356e14d7216209a6c
Issue Description:
We recently hit an error where we passed an invalid module to -add_ast_path, this was completely our fault but it was a bit harder to debug because of the generic messages from LLDB. In the console once we stopped at a breakpoint you see:
With the lldb types log we see this log
llvm-project/lldb/source/Plugins/TypeSystem/Swift/SwiftASTContext.cpp
Line 4059 in 227d496
It would be great if the path to the invalid module was produced in one or both of these logs so that it would be some extra info to help debug. I was able to correlate the ordering of the logs from the types log with the output of `dsymutil -s binary | grep AST` to find the invalid module.
The text was updated successfully, but these errors were encountered: