Troubleshooting SourceKitten on Linux
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.4k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am having hard time troubleshooting SourceKitten module-info command on Linux.
I would like to read module info of a C (system library) module, Swift module and Foundation module on both macOS and Linux.
I have no issues on macOS. It also works on one Ubuntu 21.04 machine but I don't know why. I was unable to get it working on any other Ubuntu 21.04 machine. (Commands I use are listed here: https://github.com/rhx/gir2swift/issues/21#issuecomment-916032763 )
YAML machine produced by SourceKitten was the same on both working and not-working Ubuntu machines. The error from SourceKit has kind sourcekitd_error_t.SOURCEKITD_ERROR_REQUEST_FAILED but carries no message.
At this point I need an advice on how to troubleshoot the sourcekitd. Is there a possibility to get some log? Should I try to build and run the sourcekitd in a debugger?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing SourceKitten's module-info command on the working and failing Ubuntu 21.04 machines, using the commands linked in the issue. Investigate whether sourcekitd exposes logs or debugger information for the request failure; done means documenting a reproducible cause and troubleshooting path, or confirming the required diagnostic steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli, devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100