Hi Henrik and list, I was just asking how can I do the research by myself to find out where the bug comes from.<div><br></div><div>Anyway, here&#39;s my config:</div><div><br></div><div>Debian GNU/Linux��wheezy/sid (testing) - Kernel version 2.6.32-5-686</div>

<div><br></div><div>CPU: Intel(R) Pentium(R) Dual ��CPU ��T3400 ��@ 2.16GHz</div><div><br></div><div>Smalltalk version &#39;Pharo1.2&#39;</div><div>Smalltalk vmVersion ��&#39;Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.35]&#39;</div>

<div><br></div><div><div class="gmail_quote">2011/3/30 Henrik Johansen <span dir="ltr">&lt;<a href="mailto:henrik.s.johansen@veloxit.no">henrik.s.johansen@veloxit.no</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div><div></div><div class="h5"><br>
On Mar 30, 2011, at 4:32 25PM, AxiNat wrote:<br>
<br>
&gt; Hi list,<br>
&gt;<br>
&gt; I was getting some random crashes in 1.1, so I switched to 1.2 some weeks ago. It&#39;s been kind of stable until just today, when it started randomly crashing again. At least the image isn&#39;t corrupted like it used to happen to me in 1.1, but I&#39;m wasting a lot of time recovering lost changes.<br>


&gt;<br>
&gt; The terminal just outputs &quot;illegal hardware instruction&quot;, how could I find out the bug&#39;s nature to fill in a bug report?<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Bernat Romagosa.<br>
<br>
</div></div>No info on OS, hardware, VM etc. you&#39;re using means you won&#39;t even getting qualified guesses as answers to this.<br>
<br>
Cheers,<br>
Henry<br>
</blockquote></div><br></div>