2016-04-05 20:48 GMT+02:00 Nicolai Hess <nicolaih...@gmail.com>: > > > 2016-04-05 20:37 GMT+02:00 Hilaire <hila...@drgeo.eu>: > >> See in the screenshot, >> >> contractRate is an instance variable. When evaluating it from the method >> variable pane, it seems to return an index. >> > > Ok, thats funny. > > >> >> When evaluating a method variable from the instance variable pane you >> get an undefined variable error... >> >> It used to be different before, and it is to say the least not >> convenient to debug >> > > I do not remember that I ever tried to evaluate a > method var / instance var > in the > instance / method > inspector pane. > > I now see the problem. For the context inspector, the compiler can generate code for evaluating the "printit on a variable" but for variables that are in fact instance variables, it does not generate an error because it resolves the variable name and index from the (object) instance scope. This is wrong I think. With that index, the code will access not the method object instance, but the context. It therefore reads some context instance data (stackpointer for exampe!).
Are you sure this ever worked? I am afraid we can not fix this. Pharo 5.0 is about to release and it contains a new Debugger. The (old) spec debugger is still there, but it does not provide the printIt/doIt commands on the isntance and context inspector panes... > > >> >> >> Hilaire >> -- >> Dr. Geo >> http://drgeo.eu >> > >
