From 07a4ac22edd3f08cb460a651a2318d9bf5090ba1 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Tue, 8 May 2012 21:25:06 +0000 Subject: Fixing a bug where the SetValueFromCString() method failed to operate on dynamic values. The fix consists in making the set operation fall through to the parent. We only actually allow this if the dynamic value is at a 0-offset from the parent, or the new value is 0. Other scenarios would need agreement on the actual meaning of the set operation (do we keep offsetting? do we just assume the user knows what they are doing?) so we prevent them, and let the expression parser deal with the complexity llvm-svn: 156422 --- lldb/scripts/Python/interface/SBValue.i | 3 +++ 1 file changed, 3 insertions(+) (limited to 'lldb/scripts/Python/interface') diff --git a/lldb/scripts/Python/interface/SBValue.i b/lldb/scripts/Python/interface/SBValue.i index d529e656099..9b9fd529de8 100644 --- a/lldb/scripts/Python/interface/SBValue.i +++ b/lldb/scripts/Python/interface/SBValue.i @@ -139,6 +139,9 @@ public: bool SetValueFromCString (const char *value_str); + bool + SetValueFromCString (const char *value_str, lldb::SBError& error); + lldb::SBTypeFormat GetTypeFormat (); -- cgit v1.2.3