1. I noticed is that all the results are stored in a dictionary of
TestResult mapping the classes to their last result. When I delete
tests, these obsolete classes remain references from the dictionary
and thus never get garbage collected. Why not save the history in a
class-instance variable
Waiting in PharoInbox
Name: PackageInfo-Alexandre_Bergel.19
Author: Alexandre.Bergel Time: 4 April 2009, 9:30:16 am
UUID: cf56dd7d-c21b-4176-a2d6-874d4544a21a Ancestors: PackageInfo-
stephane_ducasse.18
Issue #712
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
I've started taking a look at the problem reported by Michael Roberts.
I got slightly different misbehavior using the 10259-ClosureBootstrap download
on linux than reported by Michael, but in checking things out I discovered that
the code in the Debugger for the *Core* downloads is different
I started a small diagnosis on the issue tracker. Some of the changes
are intentional. The closure image introduces a layer of indirection
to get out the offsets for highlighting code. I think the next place
to check is the compiler/ method changes since I think that's where
they come from but I
Stéphane,
What image did the changes come from? Presumably there are also changes that
have been made to the pharo image that are not compatible with the new code ...
I've 'fixed' the obvious problems in the changes that were in the install
changeSet, but that didn't fix the 'step into'
