<br><br><div class="gmail_quote">On Fri, Apr 26, 2013 at 9:25 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Frank are you saying that, under Ubuntu 13.04, after writing to a<br>
particular place in a file, if you subsequently go back and _read_<br>
from that place, even using the same ReadWriteStream instance, that it<br>
will not read back in what was just written until a #flush occurs?<br>
<br>
Hopefully that is not the case!<br></blockquote><div><br></div><div>If it is, it is an ubuntu bug and not one we should work around, no?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
On Fri, Apr 26, 2013 at 5:17 AM, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
> On 25 April 2013 15:35, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
>> On 25 April 2013 13:54, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>>><br>
>>> On Thu, Apr 25, 2013 at 02:18:22PM +0200, Bert Freudenberg wrote:<br>
>>>><br>
>>>> This didn't sound like a VM problem at first, but according to the discussion it is:<br>
>>>><br>
>>>> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=956376" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=956376</a><br>
>>>><br>
>>>> Any idea?<br>
>>>><br>
>>><br>
>>> On my 64-bit Linux with an interpreter VM compiled in 64-bit, and using<br>
>>> Squeak - no problem. With a 32-bit interpreter - no problem. With Cog -<br>
>>> again, no problem.<br>
>>><br>
>>> I edited the class comment for class Array in each case.<br>
>>><br>
>>> Dave<br>
>><br>
>> "Error: RemoteString past end of file" can indicate a broken/damages<br>
>> changes file.<br>
>><br>
>> It does when I get the error, at least. Usually that happens when I<br>
>> have to hard-kill an image that's stored state in the changes file.<br>
>> Restarting the image means there's a mismatch somehow in the state<br>
>> between the image and the changes file. Once you get one of these<br>
>> you're nearly completely hosed: you can't file things out, for<br>
>> instance.<br>
><br>
> For those not following the Pharo list, it looks like the root cause<br>
> is that the glibc in Ubuntu 13.04 doesn't immediately write new<br>
> content out to the file. Thus you can "write" to the file, and then<br>
> read from the file, only your RemoteString starts off the end of the<br>
> file. The fix is to make WriteStream >> #nextPutChunk: call "self<br>
> flush". I've pushed a 4.5 fix to trunk, but have not yet done the same<br>
> for the 4.4 and 4.3 update streams.<br>
><br>
> frank<br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>