No subject

sump.org about using RXTX.  Looks like their code may be doing something
that RXTX native code isn't tolerating?  (Read past the end of the byte[]
buffer array?  that's pretty weird.  esp for an integer. may be a buffer
handling bug of theirs.)

RXTX has been on the same version for years, so for that reason I expect
that there's no issue with its versions.

Couple notes, may be useful.
John

--000feaf0634a6577f604863ef617
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"b=
order-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddin=
g-left: 1ex;">
j =A0gnu.io.RXTXPort.readByte()I+0<br>
j =A0gnu.io.RXTXPort$SerialInputStream.read()I+61<br>
j =A0org.sump.analyzer.Device.readInteger()I+11<br>
j =A0org.sump.analyzer.Device.run()Lorg/sump/analyzer/CapturedData;+31<br>
j =A0org.sump.analyzer.DeviceController.run()V+58<br>
j =A0java.lang.Thread.run()V+11<br>
<br></blockquote><div><br>From looking at this I&#39;d guess the first path=
 is to check with folks at <a href=3D"http://sump.org">sump.org</a> about u=
sing RXTX.=A0 Looks like their code may be doing something that RXTX native=
 code isn&#39;t tolerating?=A0 (Read past the end of the byte[] buffer arra=
y?=A0 that&#39;s pretty weird.=A0 esp for an integer. may be a buffer handl=
ing bug of theirs.)<br>

<br>RXTX has been on the same version for years, so for that reason I expec=
t that there&#39;s no issue with its versions.<br><br></div></div>Couple no=
tes, may be useful.<br>John<br><br>

--000feaf0634a6577f604863ef617--