Thing is, it happens also with an older VM :(

Esteban

> On 15 Jan 2019, at 13:00, Max Leske <maxle...@gmail.com> wrote:
> 
> Actually, I think it's rather a VM problem...?
> 
> 
> On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:
> 
>> Hello,
>> 
>> I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
>> After doing
>> 
>> Stdio stdout << ‘OK’
>> 
>> I’m having this stack:
>> 
>> File class(ProtoObject)>>primitiveFailed:
>> File class(ProtoObject)>>primitiveFailed
>> File class>>fileDescriptorType:
>> File class>>fileDescriptorIsAvailable:
>> Stdio class>>standardIOStreamNamed:forWrite:
>> Stdio class>>stdout
>> UndefinedObject>>DoIt
>> OpalCompiler>>evaluate
>> RubSmalltalkEditor>>evaluate:andDo:
>> RubSmalltalkEditor>>highlightEvaluateAndDo:
>> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
>> MorphicAlarm(MessageSend)>>value
>> MorphicAlarm>>value:
>> WorldState>>triggerAlarmsBefore:
>> WorldState>>runLocalStepMethodsIn:
>> WorldState>>runStepMethodsIn:
>> WorldMorph>>runStepMethods
>> WorldState>>doOneCycleNowFor:
>> WorldState>>doOneCycleFor:
>> WorldMorph>>doOneCycle
>> WorldMorph class>>doOneCycle
>> [ [ WorldMorph doOneCycle.
>> Processor yield.
>> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ 
>> [ WorldMorph doOneCycle....
>> [ self value.
>> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self 
>> value....
>> 
>> Con someone confirm or refute this?
>> 
>> Thanks!
>> Esteban
> 


Reply via email to