<br><br><div class="gmail_quote">On Sun, Jan 2, 2011 at 4:11 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 3 January 2011 00:15, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
> Hi Martin, Hi All,<br>
> so find new VMs in VM.r2341/. The linux crashes (certainly the one you<br>
> suffered from Martin) seem to be caused by an optimization bug (but they<br>
> could be caused by bad code generation, creating something that assumes<br>
> ordering constraints which C doesn't guarantee). I suspect the former<br>
> because I don't see the crash when running exactly the same VM and image<br>
> from a different directory; provoking the crash requires a particular path<br>
> (go figure; I haven't pinned this down yet).<br>
> So my "fix" is preventing a complex function being inlined into the main<br>
> interpreter loop, removing the sources of some warnings, and lowering the<br>
> optimization level of the gcc3x-cointerp.c file to -O1 from -O2 (my build<br>
> environment, CentOS Linux 5.3, uses gcc 4.1.2). I'm not proud of this<br>
> "fix". I've violated the Deutsch criterion by not diagnosing the cause of<br>
> the bug so I can't stand behind this fix; it's a hack that appears to work<br>
> and may have merely pushed the real bug further underground. Alas I don't<br>
> have time to do a better job. Hopefully it'll get those of you on linux<br>
> going again.<br>
<br>
</div>Eliot, if you remember, i also had crash issues on linux, and pinned down it to<br>
removing optimization from <something>heartbeat.c while keeping<br>
gcc3x-cointerp.c to use<br>
same optimization flags as for rest of files.<br>
<br>
I will start coding cmake config for Cog during next week and will be<br>
able to check my previous<br>
observations again.<br></blockquote><div><br></div><div>That would be really great. The crash Martin and others was seeing was a) in evaluating Process>priority: #>= ended up getting sent to the Processor and in the subsequent attempt to raise a notifier for the doesNotUnderstand: the VM crashed in MethodContext>>tempNames. I only saw this crash using the Pharo1.1 one click installed in /pub/mkobetic/st/pharo /and/ the VM installed in /pub/mkobetic/st/pharo/coglinux. This was compiled with gcc 4.1.2, -O2.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> best<br>
> Eliot<br>
> On Sat, Jan 1, 2011 at 11:16 PM, <<a href="mailto:mkobetic@gmail.com">mkobetic@gmail.com</a>> wrote:<br>
<br>
</div><div><div></div><div class="h5">--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
<br>
</div></div></blockquote></div><br>