kuilpd wrote: @Michael137 Still not sure about the ways things can be printed part, but here are the motivational examples:
* `DWIMPrint` calls `frame var` only for expressions that have variables and member retrievals with the `.` operator, so it will be using the `simple` mode to call DIL. * `lldb-dap` and its tests expect only the capabilities of old `frame var` and attempt to evaluate expressions using `frame var` without any checks, with a fallback to full expression evaluation. To maintain the tests and to limit the subset of expressions evaluated by DIL, `lldb-dap` will be calling it using the `legacy` mode (which replicates what old `frame var` could do). * The actual `frame var` console command should always use the full DIL capabilities, so it will be calling DIL in `full` mode. Should I add this to commit description? Make it shorter or more verbose? https://github.com/llvm/llvm-project/pull/178747 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
