-
Notifications
You must be signed in to change notification settings - Fork 70
Improve support for debuggers #352
Copy link
Copy link
Open
Labels
A-frameworkAffects the framework crates and the translator for themAffects the framework crates and the translator for themA-objc2Affects the `objc2`, `objc2-exception-helper` and/or `objc2-encode` cratesAffects the `objc2`, `objc2-exception-helper` and/or `objc2-encode` cratesenhancementNew feature or requestNew feature or request
Milestone
Description
Metadata
Metadata
Assignees
Labels
A-frameworkAffects the framework crates and the translator for themAffects the framework crates and the translator for themA-objc2Affects the `objc2`, `objc2-exception-helper` and/or `objc2-encode` cratesAffects the `objc2`, `objc2-exception-helper` and/or `objc2-encode` cratesenhancementNew feature or requestNew feature or request
It would be especially cool if we could re-use the debugging support that LLDB already contains for Foundation types like
NSStringandNSArray.The unstable
#![debugger_visualizer]attribute is probably the way to go, once it supports LLDB. Support for other debuggers is also desired, but probably less important (since the expectation is that users are going to be developing on macOS).LLDB has a way to change how types are debugged, so I might try writing a python script that users can
command script import(similar to how Rust's LLDB support currently work, though I think we might need to improve that too, see also vadimcn/codelldb#997).Seems like Swift does it in code somehow, see https://developer.apple.com/documentation/swift/debugdescription(). So might be possible to make this information part of the binary?