Hi,
I've made a java program to communicate with a modem under WinXP and works
fine. I've used Java commapi. Now, I've to run the same program under linux.
I've downloaded what I need like indicate on http://www.rxtx.org/ and on
http://wass.homelinux.net/howtos/Comm_How-To.shtml, but it doesn't work.
This is the error that Eclipse console give me:
#
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x40008483, pid=5201, tid=1075164800
# Java VM: Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode, sharing)
# Problematic frame:
# C [ld-linux.so.2+0x8483]
# An error report file with more information is saved as hs_err_pid5201.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Could you help me? Thanks in advance for your suggestions.
Stefan Schulz - 07 Jun 2005 00:43 GMT
> #
> # An unexpected error has been detected by HotSpot Virtual Machine:
[quoted text clipped - 7 lines]
>
> Could you help me? Thanks in advance for your suggestions.
Looks like someone screwed up their JNI code, majorly. Take a look at the
error file, and if you can figure out what went wrong, good for you.
Otherwise, submit the error to your library's vendor, and hope for a fix. :)

Signature
In pioneer days they used oxen for heavy pulling, and when one ox
couldn't budge a log, they didn't try to grow a larger ox. We shouldn't
be trying for bigger computers, but for more systems of computers.
--- Rear Admiral Grace Murray Hopper
Dale King - 07 Jun 2005 02:52 GMT
> Hi,
>
[quoted text clipped - 15 lines]
>
> Could you help me? Thanks in advance for your suggestions.
My advice is to lose Sun's lousy, antiquated JavaComm API altogether and
just stick with RXTX. In other words just use RXTX without the JavaComm
wrapper on both Linux and Windows.

Signature
Dale King
Roby - 07 Jun 2005 09:55 GMT
Thanks Dale! Now I only use RXTX and works fine under linux too. Although,
there is a RXTX warning when I open the serial port:
RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyS0
Is it a problem?
>> Hi,
>>
[quoted text clipped - 21 lines]
> just stick with RXTX. In other words just use RXTX without the JavaComm
> wrapper on both Linux and Windows.
The Wogster - 07 Jun 2005 13:50 GMT
> Thanks Dale! Now I only use RXTX and works fine under linux too. Although,
> there is a RXTX warning when I open the serial port:
>
> RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyS0
>
> Is it a problem?
That warning usually means that some program or process created a lock
file to indicate the port was in use, but never cleaned up after itself
when that process ended. RXTX noticed that the lock file was not being
held by any process, so it deleted it.
You may want to check and make sure that your program is deleting it's
own lock when it ends. If the library doesn't do it, just make sure you
delete it yourself.
W
Dale King - 08 Jun 2005 04:13 GMT
> Thanks Dale! Now I only use RXTX and works fine under linux too. Although,
> there is a RXTX warning when I open the serial port:
>
> RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyS0
>
> Is it a problem?
I don't know any specifics as I use it under Windoze, but I see various
places in the change log talking about various lock file fixes. There
are some things that have to be done to use lock files. See the Install
file in the RXTX distribution.

Signature
Dale King