I see the following ways in which Apple could fix lldb issues
1 go back to gdb
2 scrap the swift runtime and make proprietary swift
runtime just like it was back in NextStep days
3 scrap swift altogether and migrate back either to objc
or some other language that is not overblown with features and has a working debugger cause it's 100% obvious now
that swift is 10 years in making that debugger is beyond repair. Amen.
sndive
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Well, it's apparent somebody in Cupertino had screwed up. Quite possibly an equal opportunity action employee.
Just stop using Swift. It's basically junk. You are describing one of the reasons why.