On Fri, Apr 26, 2013 at 9:25 AM, Chris Muller asqueaker@gmail.com wrote:
Frank are you saying that, under Ubuntu 13.04, after writing to a particular place in a file, if you subsequently go back and _read_ from that place, even using the same ReadWriteStream instance, that it will not read back in what was just written until a #flush occurs?
Hopefully that is not the case!
If it is, it is an ubuntu bug and not one we should work around, no?
On Fri, Apr 26, 2013 at 5:17 AM, Frank Shearar frank.shearar@gmail.com wrote:
On 25 April 2013 15:35, Frank Shearar frank.shearar@gmail.com wrote:
On 25 April 2013 13:54, David T. Lewis lewis@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
vm-dev@lists.squeakfoundation.org