Fixing a problem where some uninitialized cases of vectors could cause diagnostic output from the synthetic children providers - this time the fix should work

llvm-svn: 154361

1 files changed, 6 insertions, 1 deletions

diff --git a/lldb/examples/synthetic/gnu_libstdcpp.py b/lldb/examples/synthetic/gnu_libstdcpp.py
index 009e39084a7..3f5916931bb 100644
--- a/lldb/examples/synthetic/gnu_libstdcpp.py
+++ b/lldb/examples/synthetic/gnu_libstdcpp.py
@@ -12,6 +12,8 @@ class StdListSynthProvider:
 	def __init__(self, valobj, dict):
 		logger = Logger.Logger()
 		self.valobj = valobj
+		self.count = None
+		logger >> "Providing synthetic children for a map named " + str(valobj.GetName())
 
 	def next_node(self,node):
 		logger = Logger.Logger()
@@ -134,7 +136,9 @@ class StdVectorSynthProvider:
 
 	def __init__(self, valobj, dict):
 		logger = Logger.Logger()
-		self.valobj = valobj;
+		self.count = None
+		self.valobj = valobj
+		logger >> "Providing synthetic children for a map named " + str(valobj.GetName())
 
 	def num_children(self):
 		logger = Logger.Logger()
@@ -228,6 +232,7 @@ class StdMapSynthProvider:
 	def __init__(self, valobj, dict):
 		logger = Logger.Logger()
 		self.valobj = valobj;
+		self.count = None
 		logger >> "Providing synthetic children for a map named " + str(valobj.GetName())
 		
 	# we need this function as a temporary workaround for rdar://problem/10801549