lldb-vscode #614
Replies: 2 comments 5 replies
-
|
Our first experience is that we very easily ran into an assertion failure (crashing on Windows). We got that fixed here: swiftlang/swift#68634 , and we're in the process of checking its usability (more news later today, hopefully). I had noticed some cosmetic oddities like optionals showing as something like We're invested using |
Beta Was this translation helpful? Give feedback.
-
|
The one thing I noticed is it doesn't seem to expand enums with associated types where the type is something more complex than a number or string. Have you seen this? |
Beta Was this translation helpful? Give feedback.
-
|
It sounds weakly familiar but I'll be able to say more next week, I spent little time with it due to the assert/crash. We're looking to switch ~10 engineers to using the new DAP so I expect we'll find a lot of things to improve. |
Beta Was this translation helpful? Give feedback.
-
|
I'm considering merging the vscode-lldb changes into the main branch. Managing two release branches is a pain. Do you have any concerns? |
Beta Was this translation helpful? Give feedback.
-
|
One concern: I'm testing right now and I can't debug tests with the codelldb adapter because |
Beta Was this translation helpful? Give feedback.
-
|
I found it, it's not directly related to the 1.6 changes, but for us it's hitting at the same time because we are trying to upgrade to a new Swift toolchain from main with a bumped version number: #618 |
Beta Was this translation helpful? Give feedback.
-
|
No concerns with merging into main. The issue I found is unrelated, though we should get the fix in a release as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
For anyone using the 1.6 pre-release on Windows. Have you used the debugger that is packaged with the swift toolchain? How does it compare to CodeLLDB?
@compnerd @tristanlabelle
Beta Was this translation helpful? Give feedback.
All reactions