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
When using a package on Swift-Colab with the build flags -c release -Xswiftc -Onone, there is an inconsistent and worsening problem with loading Swift modules into LLDB. You have to restart the runtime and re-install the packages, sometimes multiple times, to make it load. This isn't that bad of an issue, because each re-install utilizes cached build products and takes only 1 second. But it is a bug.
I suspect that this is not a fault of Swift-Colab, but rather a fault of the Swift compiler, SwiftPM, or LLDB. Due to the bug's nature, it will be difficult to narrow down. Please read through conversation on philipturner/swift-colab#15 for the full details on this bug.
Environment (please complete the following information):
OS: Ubuntu 18.04, x86_64 (Google Colab)
First affected S4TF: 2021-11-12 nightly snapshot
First affected SwiftPlot: 2021-12-23 nightly snapshot
The text was updated successfully, but these errors were encountered:
philipturner
added
the
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
label
Jun 18, 2022
philipturner
changed the title
Won't import C-dependent package into LLDB unless debug symbols are present
LLDB doesn't import C-dependent package unless debug symbols are present
Jun 18, 2022
Describe the bug
When using a package on Swift-Colab with the build flags
-c release -Xswiftc -Onone
, there is an inconsistent and worsening problem with loading Swift modules into LLDB. You have to restart the runtime and re-install the packages, sometimes multiple times, to make it load. This isn't that bad of an issue, because each re-install utilizes cached build products and takes only 1 second. But it is a bug.I suspect that this is not a fault of Swift-Colab, but rather a fault of the Swift compiler, SwiftPM, or LLDB. Due to the bug's nature, it will be difficult to narrow down. Please read through conversation on philipturner/swift-colab#15 for the full details on this bug.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: