Comment by aaron crespo (JIRA)

I can't include the projects but I can describe how they are setup.

Create Framework project, SUPPORTED_PLATFORMS: [watchsimulator watchOS iphonesimulator phones appletvsimulator appletvos]
Using carthage add some Library dependencies (that are swift) (for example RxSwift, Quick, Nimble)
Link them according to carthage Documentation
$ carthage bootstrap make sure to use binaries.

Create a test target with a breakpoint.

The debugger should show the behavior when entered.

This might happen with SwiftPM when using artifacts produced by its builds.

These are the usual "crashing in deserialization" bugs when we don't have sensible build settings, or where one of the frameworks appears to have changed.

Comment by stephen (JIRA)

@belkadan could you expand on your sensible build settings comment? I'm getting the same issue here with a large project with a number of carthage dependencies. You also mention in similar issue thread that it's possible to enable logging for lldb. Can you point me at anything that explains how to do this?

Comment by stephen (JIRA)

I've found the issue that was causing this for me. The pods subproject debug-information-format had got changed to "DWARF with dSYM" when the main project was on "DWARF". Changing both to DWARF fixed it.

Sorry for being unclear. The build settings comment was a reference to a vague collection of problems that are sometimes the developer's fault and sometimes the compiler's fault, usually where certain framework headers are found both in the built framework and in the source directory, or where the user is writing custom module maps to access non-modular content but LLDB fails to pick up those custom module maps.

I am a little surprised that this is causing crashes rather than just failures to load information.