I’ve encountered a situation where pharo crashes, and when I run it from 
command line I get: "Segmentation fault: 11". Also before that some trace 
appears starting with highlighted: "MessageNotUnderstood: 
ToolDockingBarMorph>>popUpEvent:in:”. I’ve also updated my Pharo launcher and 
now stack trace disappeared (probably because now I have to specify some flag), 
but the problem remains. Should I report this to pharo issue tracker, or this 
is a VM problem and it should be handled in a different way?

Uko

Reply via email to