Am 26.09.2006 um 10:23 schrieb Giovanni Corriga:

> Il giorno lun, 25/09/2006 alle 20.13 -0400, Milan Zimmermann ha  
> scritto:
>> On 2006 September 25 17:26, Giovanni Corriga wrote:
>>> Il giorno lun, 25/09/2006 alle 13.42 -0700, Brad Fuller ha scritto:
>>>> stephane ducasse wrote:
>> <<snip>>
>>>>
>>>> The code is in the mantis defect that is 100% reproducible on my  
>>>> PC. I
>>>> think it's easy to duplicate or make other PCs crash.
>>>
>>> I can reproduce it on my system, (Fedora Core 5, 3.9-7 vm, 3.8  
>>> image).
>>
>> Guys,
>>
>> Could you paste the exact output of "squeak -version"? - The  
>> reason I am
>> saying it is that this _does_ work on my SuSE 9.3. I think there  
>> are multiple
>> 3.9-7 VMs, and we already saw significant performance difference  
>> between 3.9
>> VM version built on RedHat (i think) and Ian's version (on another  
>> thread
>> this week named something like Squeak is slooow):
>
> Ok, here's mine:
>
> [gcorriga at rincewind ~]$ squeak -version
> 3.9-7 #1 Thu May 18 12:06:33 CEST 2006 gcc 4.1.0
> Squeak3.9alpha of 4 July 2005 [latest update: #7021]
> Linux rincewind 2.6.16-1.2111_FC5.stk16 #1 Mon May 8 10:49:23 EDT 2006
> i686 i686 i386 GNU/Linux
> default plugin location: /usr/lib/squeak/3.9-7/*.so
>
> could this be related to the use of gcc 4.x?

AFAIK it's not related to the Squeak binary at all but just depends  
on the system. The problem started to pop up only recently (a year or  
maybe two ago). Maybe it's kernel 2.6 related or something else that  
changed in Linux recently - or simply that people have more than 2 GB  
virtual memory nowadays.

The problem always occurs when Squeak is loaded partially around the  
2 GB limit. The fix for the problem at hand would be a code audit in  
the FloatArray plugin, converting ints to unsigned where necessary.

- Bert -