eclipse crashes on loading on serial terminal

[Ash Charles]

When I open a connection to a USB serial port using the RXTX (http://rxtx.qbang.org/eclipse) and the Target Manager Terminal plugins, Eclipse consistently crashes with no error messages. The follow log is generated:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f4dbd46524d, pid=4074, tid=139971864680208
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18-1.8-0ubuntu1
# Problematic frame:
# C [librxtxSerial.so+0x724d] read_byte_array+0x3d
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Note, I have not had the same problem on 32bit Karmic on a different machine. I'm able to connect with no problems using ckermit.
Thanks.

[Matthias Klose (doko)]

the error log is missing.
is this a locally installed version of eclipse or the one distributed in lucid?

[Ash Charles (ashcharles)]

I believe this was the version of Eclipse distributed with Lucid.

-Ash

On Wed, Jul 14, 2010 at 4:18 AM, Matthias Klose
<email address hidden> wrote:
> the error log is missing.
> is this a locally installed version of eclipse or the one distributed in lucid?
>
>
> ** Changed in: openjdk-6 (Ubuntu)
>       Status: New => Incomplete
>
> --
> eclipse crashes on loading on serial terminal
> https://bugs.launchpad.net/bugs/593172
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “openjdk-6” package in Ubuntu: Incomplete
>
> Bug description:
> When I open a connection to a USB serial port using the RXTX (http://rxtx.qbang.org/eclipse) and the Target Manager Terminal plugins, Eclipse consistently crashes with no error messages.  The follow log is generated:
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f4dbd46524d, pid=4074, tid=139971864680208
> #
> # JRE version: 6.0_18-b18
> # Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
> # Derivative: IcedTea6 1.8
> # Distribution: Ubuntu lucid (development branch), package 6b18-1.8-0ubuntu1
> # Problematic frame:
> # C  [librxtxSerial.so+0x724d]  read_byte_array+0x3d
> #
> # If you would like to submit a bug report, please include
> # instructions how to reproduce the bug and visit:
> #   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>
> Note, I have not had the same problem on 32bit Karmic on a different machine.  I'm able to connect with no problems using ckermit.
> Thanks.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/593172/+subscribe
>

[Launchpad Janitor (janitor)]

[Expired for openjdk-6 (Ubuntu) because there has been no activity for 60 days.]

[Gregor Riepl (onitake)]

Reopening, as the problem is affecting me too. Same behavior, same crash location.

I've attached my crash log to complete the report.

[Gregor Riepl (onitake)]

Reopening with complete crash log

[Gregor Riepl (onitake)]

The crash is coming from a broken rxtx library installed from http://rxtx.qbang.org/eclipse/.

If I remove ~/.eclipse/org.eclipse.platform_3.7.0_155965261/plugins/gnu.io.rxtx.linux.x86_64_2.1.7.3_v20071015/os/linux/x86_64/*.so and symlink the packaged libraries from /usr/lib/jni/librxtx*.so (Ubuntu package librxtx-java), it works. A version mismatch warning will be printed out, but no error and no crash happens.

Removing the "RXTX end-user runtime" plugin in Eclipse does not help, because "Target Management Terminal" depends on it for serial connections. The plugin was created to remedy https://bugs.eclipse.org/bugs/show_bug.cgi?id=175336 - but this does not account for situations where the rxtx libraries are installed in the system JNI library directory. Someone should open a new bug report on the Eclipse bug tracker to request a fix for this.

[Gregor Riepl (onitake)]

I create a bug report on eclipse.org to make the developers aware of the problem and suggest checking for both Eclipse and system RXTX libraries instead: https://bugs.eclipse.org/bugs/show_bug.cgi?id=372655

[Gregor Riepl (onitake)]

The plugin works as expected, according to Martin and my own tests. It will automatically pick up a system RXTX if Eclipse finds one.

Unfortunately, Eclipse seems to be hitting a little problem with OpenJDK's extension path: It contains /usr/java/packages/lib/ext - hardcoded into /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so - but that is not used on Debian/Ubuntu. Any Java extensions installed via the package manager are put into /usr/share/java. I don't know if this is intended or not.

As a temporary workaround, I found it to be easiest and least intrusive to just symlink RXTXcomm.jar to /usr/java/packages/lib/ext. Perhaps there is a way to smash it into the Eclipse classpath, but I haven't found a proper way to do so.

Paste this into your terminal, restart Eclipse and you're good to go:
sudo mkdir -p /usr/java/packages/lib/ext
sudo ln -s /usr/share/java/RXTXcomm.jar /usr/java/packages/lib/ext/

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.