Now, i'm pretty sure it is the second option (some shared state
somewhere in the library). I've searched google and the only problems
i can find are of the "same object" variety, and the problem appears
reliably (across computers) and it's definitely not the same object,
so it's probably some share
Paulo Levi wrote:
Hi a bug, i've been seeing:
First a simplification:
Two different RandomAccessFile objects, inited in "r" mode and
pointing to the same file appear to be interfering on on their reads
(concurrent threads). They both manipulate the file pointer i guess,
but i expected nothing ba
Hi a bug, i've been seeing:
First a simplification:
Two different RandomAccessFile objects, inited in "r" mode and
pointing to the same file appear to be interfering on on their reads
(concurrent threads). They both manipulate the file pointer i guess,
but i expected nothing bad to happen, because
