Sean Allen wrote: > Just as a bit more info. I used squeak for several months without ever > seeing this error. > I used pharo for 3 months without seeing this error. I've only gotten > this error in the latest images > with the latest vm and get it constantly. Not occassionally, I can get > this to happen at least > once every 120 seconds or so, sometimes more often. It would seem to be > as an outsider, > that something must have changed.
it definitely sounds like it. Would be good to investigate what might have changed in the call path that *sets* the variable to check why it is ending up being nil. Maybe it shouldn't be set or initialized to nil but to an empty collection in those cases? Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
