Frank,

Can you please clarify if this is a bug that has been observed with any of
the *existing* pre-compiled VMs obtained from either http://squeakvm.org/unix/
or from http://www.mirandabanda.org/files/Cog/VM/?

Adding a workaround to one spot in the image may be the wrong thing to do.
It would mask a serious problem that could lead to data corruption for
anyone who relies on storing data in files.

I am traveling and will not be able to follow up on this mail for a while,
but please - if this is a gcc optimizer problem, as has been suggested
elsewhere in the discussion, then let's not "fix" it in the image.

Dave


On Fri, Apr 26, 2013 at 01:52:55PM +0100, Frank Shearar wrote:
> Agreed. It's more complicated than it sounds, of course: the proper
> fix is to push out new updated binaries to ftp.squeak.org.
> 
> frank
> 
> On 26 April 2013 13:17, Pavel Krivanek <squeak1 at continentalbrno.cz> wrote:
> > Please submit then info to redhat bugzilla about where Jaroslav can find the
> > fixed 4.3 image to repack it.
> >
> > -- Pavel
> >
> >
> > On Fri, Apr 26, 2013 at 12:17 PM, Frank Shearar <frank.shearar at gmail.com>
> > wrote:
> >>
> >> On 25 April 2013 15:35, Frank Shearar <frank.shearar at gmail.com> wrote:
> >> > On 25 April 2013 13:54, David T. Lewis <lewis at mail.msen.com> wrote:
> >> >>
> >> >> On Thu, Apr 25, 2013 at 02:18:22PM +0200, Bert Freudenberg wrote:
> >> >>>
> >> >>> This didn't sound like a VM problem at first, but according to the
> >> >>> discussion it is:
> >> >>>
> >> >>> https://bugzilla.redhat.com/show_bug.cgi?id=956376
> >> >>>
> >> >>> Any idea?
> >> >>>
> >> >>
> >> >> On my 64-bit Linux with an interpreter VM compiled in 64-bit, and using
> >> >> Squeak - no problem. With a 32-bit interpreter - no problem. With Cog -
> >> >> again, no problem.
> >> >>
> >> >> I edited the class comment for class Array in each case.
> >> >>
> >> >> Dave
> >> >
> >> > "Error: RemoteString past end of file" can indicate a broken/damages
> >> > changes file.
> >> >
> >> > It does when I get the error, at least. Usually that happens when I
> >> > have to hard-kill an image that's stored state in the changes file.
> >> > Restarting the image means there's a mismatch somehow in the state
> >> > between the image and the changes file. Once you get one of these
> >> > you're nearly completely hosed: you can't file things out, for
> >> > instance.
> >>
> >> For those not following the Pharo list, it looks like the root cause
> >> is that the glibc in Ubuntu 13.04 doesn't immediately write new
> >> content out to the file. Thus you can "write" to the file, and then
> >> read from the file, only your RemoteString starts off the end of the
> >> file. The fix is to make WriteStream >> #nextPutChunk: call "self
> >> flush". I've pushed a 4.5 fix to trunk, but have not yet done the same
> >> for the 4.4 and 4.3 update streams.
> >>
> >> frank
> >>
> >
> >
> >
> >