can you try on something less sensitive than copyFrom:to: to debug it? Stef On Nov 14, 2008, at 4:59 PM, Antoine Marot wrote:
Hi all,
I have a very strange bug when I use method wrappers.
Here is my wrapper code (actually it does nothing but calling the method) :
ProtoObject variableSubclass: #Wrapper instanceVariableNames: 'compiledMethod' classVariableNames: '' poolDictionaries: '' category: 'Wrapper-Core'
Wrapper>>#doesNotUnderstand: aMessage ^aMessage sendTo: compiledMethod
Wrapper>>#run: aSymbol with: arguments in: rec ^rec withArgs: arguments executeMethod: compiledMethod
Wrapper>>#compiledMethod: c compiledMethod:=c. ^self
Now I want to execute this :
SequenceableCollection methodDict at: #copyFrom:to: put: (Wrapper new compiledMethod: (SequenceableCollection>>#copyFrom:to:)).
It works fine with a new pharo-dev image. But if I install ByteSurgeon before that, it crashes the VM if I click on the workspace for instance.
I just don't know what possibly happen, any help would be very appreciated :)
Regards,
Antoine
------ Antoine Marot Ph.D Student Université Libre de Bruxelles Département d'Informatique _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project