David T. Lewis a écrit :
> On Sat, Aug 28, 2004 at 05:58:11PM -0700, Tim Rowledge wrote:
> 
>>"David T. Lewis" <lewis at mail.msen.com> wrote:
>>
>>
>>>Bonjour,
>>>
>>>This is only a guess, but it looks like some kind of problem loading image
>>>segments from disk.
>>
>>It looks like the same problem I occasionally get because the squeak
>>object memory wraps over the 2Gb line; a small part of the segment
>>loading prim goes bad if the addresses seem to be -ve int values. I'm
>>sure we discussed this on-list some time ago but I can't actually find
>>relevant mails right now. It is quite remarkable how few problems are
>>caused by this effect. 
> 
> 
> Ah, yes, that's probably it. If I recall, the problem showed up for people
> running the newer Linux 2.6 kernels (maybe only on 64 bit machines? I'm
> not sure).  If I remember right, I think that it was possible to work around
> the problem by forcing the VM to use a fixed memory allocation, something
> like "squeak -memory 40m myimage". I don't happen to have a Linux 2.6
> system or a 64 bit machine to confirm this, but it's worth trying the
> " -memory" option to see if it helps.
> 
> Damien, essayez ceci:
> 
>   $ squeak -memory 40m squeak.image
> 
> Dave
>



$ squeak -version
3.7b-5 #1 Mon Jul 19 20:31:04 PDT 2004 gcc 3.3.4
Squeak3.7beta of '1 April 2004' [latest update: #5868]
Linux gadget.dnsalias.net 2.4.26 #15 Wed Jun 23 08:06:00 PDT 2004 i686 
GNU/Linux
default plugin location: /usr/lib/squeak/3.7b-5/*.so
$ uname -r
2.6.4-ck1
$ squeak -memory 40m squeak.image
I test this command, but squeak bug immediately. I have joined, the 
debug.log.


Thanks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SqueakDebug.log
Type: text/x-log
Size: 3933 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20040829/12a8061a/SqueakDebug.bin