Am 27.09.2006 um 01:01 schrieb tim Rowledge:

>
> On 26-Sep-06, at 3:11 PM, Brad Fuller wrote:
>
>>>
>>> and see if it can give us the stack in hex.
>> [bfuller at ives bld]$ ./squeak /home/bfuller/projects/squeak/images/ 
>> Squeak3.9g-7060.image
>>
>> sweep failed to find exact end of memory
>>
>> 813821F4 Morph>hasDropShadow
>> 81381ABC Morph>fullDrawOn:
>> 81381A60 Canvas>fullDraw:
>> 81381A04 Canvas>fullDrawMorph:
>
> Thanks Brad. That 128-and-a-bit Mb jump is definitely puzzling.  
> That's a lot of allocations between the start of doOneCycleNowFor:  
> and displayWorldSafely:

Wasn't the test case to allocate some huge FloatArrays? Might explain  
the jump. And the crash, if the arrays are allocated across the 2GB  
border.

- Bert -