[Lldb-commits] [lldb] [lldb] Report a scripted frame's variables with the frame's value type (PR #221708)
Med Ismail Bennani via lldb-commits
lldb-commits at lists.llvm.org
Tue Sep 8 15:46:39 PDT 2026
================
@@ -52,6 +52,17 @@ class ScriptedFrameInterface : virtual public ScriptedInterface {
virtual lldb::ValueObjectListSP GetVariables() { return nullptr; }
+ /// Choose which kind of variable \a value is presented as, for instance
+ /// \a eValueTypeVariableLocal to have it listed among the frame's locals.
+ ///
+ /// Include \a eValueTypeSyntheticFlag for a value the implementation built
+ /// itself. That flag is what exempts a variable from the scope rules a
+ /// declared variable is subject to, so a value with no storage behind it will
+ /// be filtered out of an in-scope-only listing without it. Leave it off to
+ /// present a variable that really does exist in the frame.
+ ///
+ /// Returning std::nullopt keeps the kind the value already reports, with the
+ /// synthetic flag added.
----------------
medismailben wrote:
I agree
https://github.com/llvm/llvm-project/pull/221708
More information about the lldb-commits
mailing list