Issue 862 in moose-technology: The GTDebugger should not break when there is an error obtaining the value of an attribute

Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Defect Priority-Medium

New issue 862 by [hidden email]: 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.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Fixed

Comment #1 on issue 862 by [hidden email]: 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

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Labels: Component-GlamorousToolkit Milestone-4.7

Comment #2 on issue 862 by [hidden email]: 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

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev