On Mon, Aug 30, 2004 at 08:13:39AM +0200, Damien Cassou wrote:
> David T. Lewis a écrit :
> > On Sun, Aug 29, 2004 at 09:32:33PM +0200, Damien Cassou wrote:
> >>David T. Lewis a écrit :
> >>>
> >>>Damien, essayez ceci:
> >>>
> >>>  $ squeak -memory 40m squeak.image
> >>
> >>$ 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.
> > 
> > I think that your system is trying to start Squeak with a script file.
> > Perhaps you did this:
> > 
> >   $ squeak -memory 40m squeak.image script
> >     => evaluate "script" on startup => BOOM
> > 
> > Or perhaps this:
> > 
> >  $ squeak -memory 40m squeak.*
> >    => squeak memory 40m squeak.image squeak.something
> >     => evavluate "squeak.something" => BOOM
> > 
> > Try to run Squeak with the exact name of the image file.
> > 
> > Essayez d'employer le nom exact "squeak.image", pas "squeak*".
> > 
> > Dave
> 
> Sorry, I did exactely what you wrote.
>  > squeak -memory 40m squeak.image

Oh, well ... I'm sorry it did not work. Perhaps someone else has an idea?
See previous email from Damien for the debug log.

The original problem seemed to be related to loading image segments, so
I had suggested running with "-memory 40m" to restrict memory ranges. This
apparently got us by the original problem, but now Damien is seeing
a problem (unrelated???) that looked to me like it might be due to Squeak
trying to read a startup script file with binary data in it. No joy, and
I'm out of ideas.

Reply in French and/or simple English if possible.

Dave