[Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

Esteban Lorenzano estebanlm at gmail.com
Tue Jan 15 12:10:44 EST 2019


Ok, it has to be me :)

Esteban

> On 15 Jan 2019, at 16:36, Martin Dias <tinchodias at gmail.com> wrote:
> 
> Hi,
> I iouldn't reproduce in macos mojave. I downloaded with:
> 
> curl https://get.pharo.org/64/70+vmLatest | bash
> 
> And no problem with
> 
> Stdio stdout << ‘OK’
> 
> Report:
> 
> ---
> Pharo7.0.0rc1
> Build information:
> Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885
> (64 Bit)
> Unnamed
> 
> CoInterpreter VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins:
> 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> 
> Mac OS X built on Jan  5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible
> Apple LLVM 7.3.0 (clang-703.0.31)
> VMMaker versionString VM: 201901051900
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5
> 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> CoInterpreter VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> ---
> 
> Martín
> 
> 
> El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano
> (estebanlm at gmail.com) escribió:
>> 
>> Thing is, it happens also with an older VM :(
>> 
>> Esteban
>> 
>>> On 15 Jan 2019, at 13:00, Max Leske <maxleske at 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
>>> 
>> 
>> 
> 




More information about the Pharo-dev mailing list