Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting
On Apr 29, 2011, at 8:18 PM, Mariano Martinez Peck wrote:
On Wed, Apr 27, 2011 at 8:31 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Apr 24, 2011, at 5:12 PM, Mariano Martinez Peck wrote:
grrrr I don't know what is happening. I am building a PharoDev 1.3 and at the end, I do: Undeclared removeUnreferencedKeys but this throws an error that I attach. It is a big loop of such error. The progress bar is showing "Clean up in DebuggerMethodMap"
So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk cleanUp.
Thanks Marcus. I don't see this commit. Did you commit it? or we lost it with the squeaksource down ?
This was part of the cleanUp improvements... some time ago. see DebuggerMethodMap>>#cleanUp Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk
cleanUp.
Thanks Marcus. I don't see this commit. Did you commit it? or we lost it
with the squeaksource down ?
This was part of the cleanUp improvements... some time ago.
see DebuggerMethodMap>>#cleanUp
ok...after looking for a while, it is never called when you do Smalltalk cleanUp: true except: #() confirming: false. I think it is because such method does: "Find all classes implementing #cleanUp or cleanUp:" classes := Smalltalk allClasses select: [:aClass| (aClass class includesSelector: #cleanUp) or: [aClass class includesSelector: #cleanUp:]]. it checks for both messages, #cleanUp: or #cleanUp But then, it does: "Run the cleanup code" classes do:[:aClass| aClass cleanUp: aggressive] displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. In your case, DebuggerMethodMap only implements #cleanUp, hence it is never called. Cheers -- Mariano http://marianopeck.wordpress.com
participants (2)
-
Marcus Denker -
Mariano Martinez Peck