[Lldb-commits] [lldb] [lldb] Limit DIL globals to only current file (PR #192592)

[Dave Lee via lldb-commits]

kastiglione wrote:

@cmtice it's not wrong, which is why this PR shifted from removing the support to making it opt-in. But there are situations where global variable access is, or may be, undesirable.

One example was given for `dwim-print`. Allowing global variable lookup is incompatible with its use case, since the lack of a local variable needs to fallback to expression evaluation (to support computed properties). Happy to go into more detailed answer for this.

Prior to DIL, `frame variable` did not support globals from another CU, that capability was reserved for `target variable`. Should `frame variable` and `target variable` continue to hold onto this distinction? If `frame variable` does indeed change to support all globals, it has to grapple with the issues Jim described. It also begs the question, why have both `target variable` and `frame variable` if the latter subsumes the former?

https://github.com/llvm/llvm-project/pull/192592