I looked more into it, and here is a smaller example: Gofer new smalltalkhubUser: 'Moose' project: 'MooseAlgos'; package: 'Moose-Algos-Graph'; load This one does open the debugger, so the other emergency evaluator issue comes from somewhere else. The problem seems to come from a Trait being defined in this package, and loading this trait triggers ClassModifiedClassDefinition which stumbles in ClassModifiedClassDefinition>>isPropagation "If there is not slot changes, I can assume that there is a propagation (the change is in one of the superclasses)" self oldClassDefinition layout ifNil: [ ^ false ]. ^ self newClassDefinition layout instanceVariables = self oldClassDefinition layout instanceVariables (the method was added 3 days ago by Ben) Doru On Sun, Jan 26, 2014 at 3:50 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
If I execute the following code in 30720: Gofer new smalltalkhubUser: 'Moose' project: 'MooseAlgos'; configuration; loadDevelopment.
I get an emergency evaluator with a strange Original error: MessageNotUnderstood Trait>>layout.
Can anyone have a look at the first one? It seems to be related to some deep code changes because the same code works find in 30714.
And also there seems to be something related to a nsWriteStream: message somewhere that breaks the Spec debugger in the same process and this is why we get an Emergency evaluator instead of the debugger.
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"