[lldb] Treat synthetic variables as locals (#204431)
From the discussion in #204177: Synthetic variables were, if they weren't variables already, created with their original type plus a flag that they're synthetic (`ValueTypeSyntheticMask`). This could lead to unexpected results. For example, when a synthetic frame would return a value derived from a global variable in `GetVariables`, the created variable would be treated as a synthetic global variable. With this PR, synthetic frames can overwrite the value type of the variables they return.
This commit is contained in:
1 parent
76968fc856
commit
45829d78f3
11 files changed
+114
-34
No files matched your search
@@ -836,6 +836,11 @@ lldb::ValueObjectListSP
|
||||
ScriptedPythonInterface::ExtractValueFromPythonObject<lldb::ValueObjectListSP>(
|
||||
python::PythonObject &p, Status &error);
|
||||
|
||||
template <>
|
||||
std::optional<lldb::ValueType>
|
||||
ScriptedPythonInterface::ExtractValueFromPythonObject<
|
||||
std::optional<lldb::ValueType>>(python::PythonObject &p, Status &error);
|
||||
|
||||
} // namespace lldb_private
|
||||
|
||||
#endif // LLDB_SOURCE_PLUGINS_SCRIPTINTERPRETER_PYTHON_INTERFACES_SCRIPTEDPYTHONINTERFACE_H
|
||||
Reference in new issue
Block a user