Re: Ridiculous readInt() bug? Read-head not advancing far enough?
- From: Thomas Weidenfeller <nobody@xxxxxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 17:43:58 +0200
El wrote:
Thats just bad. You understand what the problem actually is?
We can only guess. E.g. is the file still written while you start to read it (maybe the OS gets confused)? Do you (accidentally) share the reference to the reader (e.g. in another thread)? Does the problem happen at some magic position in the file (multiple of 512 bytes, 1k, 2k, 1G, etc.)?
Does it happen only if you read the file from the particular file system? Can you change the type of the file system? Is that by any change a network mounted / shared file system? Does it happen with different hard drives, or only with one particular drive? Does it happen on different machined / different motherboards, or only a particular one, or ones of a particular type? Does it happen with other VMs, too? Are you absolutely sure the input data is correct?
You best bet would be to manage to create a stand-alone test case which reproduces the bug, at least most of the time, in an acceptable time frame. From that you have a much better change to work.
/Thomas
-- The comp.lang.java.gui FAQ: ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq .
- References:
- Prev by Date: Re: Ridiculous readInt() bug? Read-head not advancing far enough?
- Next by Date: Re: converting int and short to byte array and vice versa
- Previous by thread: Re: Ridiculous readInt() bug? Read-head not advancing far enough?
- Next by thread: Re: Ridiculous readInt() bug? Read-head not advancing far enough?
- Index(es):
Relevant Pages
|
