From d1109c50e09b66ca6fed3fb5f5ac133211b70c2d Mon Sep 17 00:00:00 2001 From: hjk Date: Mon, 1 Aug 2016 12:22:26 +0200 Subject: Debugger: Deactivate metaObject extraction by inferior call This seems to have side-effects on memory contents. Right now it is unclear what happens exactly, so revert for 4.1rc. Change-Id: I7b1b8e376ac84b6656b1abdae720d7bead1c0b89 Reviewed-by: Christian Stenger --- share/qtcreator/debugger/dumper.py | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'share') diff --git a/share/qtcreator/debugger/dumper.py b/share/qtcreator/debugger/dumper.py index dfb4ca26aa..ac9d2b59fa 100644 --- a/share/qtcreator/debugger/dumper.py +++ b/share/qtcreator/debugger/dumper.py @@ -1351,6 +1351,11 @@ class DumperBase: return True def extractMetaObjectPtrFromAddress(): + return 0 + # FIXME: Calling "works" but seems to impact memory contents(!) + # in relevant places. One symptom is that object name + # contents "vanishes" as the reported size of the string + # gets zeroed out(?). # Try vtable, metaObject() is the first entry. vtablePtr = self.extractPointer(objectPtr) metaObjectFunc = self.extractPointer(vtablePtr) -- cgit v1.2.1