Details
-
Bug
-
Resolution: Cannot Reproduce
-
P2: Important
-
Qt Creator 4.0.0-rc1
-
None
-
Windows 7 64 bit
Qt 5.6.0
MinGW 4.9.2
gdb 7.8.1
-
3a7ce3f5be9af510634ae018e27d3b1a2970063a
Description
- Open "simple" project from tests\manual\debugger\simple\simple.pro in Creator's repository.
- Place a breakpoint at BREAK_UNINITIALIZED_HERE in testUninitialized() (line 5310).
- Let the debugger run into this breakpoint.
In Locals and Expressions view, you can see the uninitialized objects. - Expand object svi.
The Locals and Expressions view turns gray and lists svi as "<not accessible>". Creator will remain busy and acquire more and more memory. According to the Debugger Log, Creator keeps fetching variables:<Rebuild Watchmodel 43727 @ 14:03:29.471 > 14:03:29.473 [1ms] 43926python theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["local","local.svi","return","inspect","watch"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"local.svi","passexceptions":0,"qobjectnames":0,"resultvarname":"","sortstructs":1,"stringcutoff":"10000","token":43926,"typeformats":{},"watchers":[]}) 14:03:29.484 <Rebuild Watchmodel 43728 @ 14:03:29.484 > 14:03:29.486 [1ms] 43927python theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["local","local.svi","return","inspect","watch"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"local.svi","passexceptions":0,"qobjectnames":0,"resultvarname":"","sortstructs":1,"stringcutoff":"10000","token":43927,"typeformats":{},"watchers":[]})
After Creator noticed that an object is not accessible, it should not try to fetch it anymore