cc @dcci

This is something that @adrian-prantl knows best.

Can you add "log enable lldb types -f /tmp/types.log" to ~/.lldbinit, relaunch lldb, reproduce the issue and upload /tmp/types.log? It will contain all the info we need to diagnose the issue.

Comment by Edward Connell (JIRA)

Okay done!

Hey thanks for checking this out.

> lldb Found 0 AST file data entries for library: /home/ed/hello/.build/debug/hello.

> lldb ((SwiftASTContext*)0x24e55f0)->GetModule('hello')
> lldb ((SwiftASTContext*)0x24e55f0)->GetModule('hello') – failed with no error

This indicates that LLDB may have had trouble finding the .swiftmodule for "hello". How did you compile your program?

Can you paste the swiftc invocation that you used for hello and then also append `-###` at the end and paste the result of that?

Comment by Edward Connell (JIRA)

I just added a terminal transcript from start to finish. I use the swift package manager to create the project. On line 16, I gedit "main.swift" and paste in the following contents.

struct MyStruct{
    var a: Int = 0
    var b: Int = 42
}

var data = MyStruct()
  
print("Hello, world! data: (data)")  // set a breakpoint here

break on line 8 and try to examine "data", it bombs.

This may be the known issue of the Swift package manager not performing the modulewrap action. I'll need to try and reproduce to confirm.

When you compile hello.swift with swiftc directly (not using swiftopm), does debugging work?

Comment by Edward Connell (JIRA)

I just tried it. Yes, using "swiftc -g main.swift" debugging works. So it's an SPM issue. I guess I will need to use an external build system like CMake. I really appreciate you helping me with this. I have to say, I am really surprised Apple would allow a product release without testing one of the most obvious features like build and debug. I also can't believe it hasn't already been fixed. Anyway, thank you so much for your help.

Have a great day, Ed

@neonichu do you have an existing swiftpm JIRA ticked this should be duped to? I think the problem here is that similar how on macOS swiftpm doesn't add -add-ast-path to the linker invocation, it (presumable) also doesn't invoke the modulewrap action on Linux.

(This could actually make for a nice starter bug?)