Status: New Owner: ---- CC: chisvasi...@gmail.com Labels: Type-Defect Priority-Medium
New issue 862 by chisvasi...@gmail.com: The GTDebugger should not break when there is an error obtaining the value of an attribute http://code.google.com/p/moose-technology/issues/detail?id=862
To reproduce do the following steps:
1. Add the method: String>>breakDebugger | aVar | self do: [:c | 1=1 ifTrue: [ self halt ] ifFalse: [ aVar := 2 ] ].
2. Execute: ['aString' breakDebugger] fork 3. In the debugger remove 'self halt' and recompile the method. 4. Select the top context
This leads to an error as 'aVar' cannot be obtained from the context.
Updates: Status: Fixed
Comment #1 on issue 862 by chisvasi...@gmail.com: The GTDebugger should not break when there is an error obtaining the value of an attribute http://code.google.com/p/moose-technology/issues/detail?id=862
Fixed in GTDebugger, still present in GTInspector
Updates: Labels: Component-GlamorousToolkit Milestone-4.7
Comment #2 on issue 862 by tu...@tudorgirba.com: The GTDebugger should not break when there is an error obtaining the value of an attribute http://code.google.com/p/moose-technology/issues/detail?id=862
Cool