Red Hat Bugzilla – Bug 555219
[abrt] crash in java-1.6.0-openjdk-1:184.108.40.206-33.b16.fc12
Last modified: 2010-03-27 11:01:10 EDT
abrt 1.0.3 detected a crash.
How to reproduce
1. Attach an Arduino Duemilanove (http://arduino.cc/) via USB.
2. Install Arduino IDE software (http://code.google.com/p/arduino/ or http://arduino.cc/en/Main/Software)
3. Follow Button State Change Detection example (http://arduino.cc/en/Tutorial/ButtonStateChange), configuring Arduino appropriately and compiling/uploading example sketch.
4. Open serial monitor window to see serial output from Arduino. (Uses RXTX at 9600bps 8N1; Arduino USB interface is FTDI.)
5. Upon pressing button (and thus generating serial output from the Arduino), JVM crashes.
Attached file: backtrace
cmdline: java -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel processing.app.Base
reason: Process was terminated by signal 6 (Aborted)
Created attachment 383592 [details]
Created attachment 383594 [details]
JVM error report
The following message was output when the JVM crashed, and I'm attaching the referenced error report file.
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007f56b0eb866d, pid=10920, tid=140010304169744
# JRE version: 6.0-b16
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
# Distribution: Custom build (Thu Nov 12 09:47:56 EST 2009)
# Problematic frame:
# C [librxtxSerial-2.1-7.so+0x866d] read_byte_array+0x3d
# An error report file with more information is saved as:
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
./arduino: line 20: 10920 Aborted (core dumped) java -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel processing.app.Base
This looks like a bug in librxtxSerial-2.1-7.so, could you look in the report file: /home/esm/ard/arduino-0017/hs_err_pid10920.log to see where it is installed? The bug should probably be reassigned to the package that provides rxtx.
That log is actually my second attachment above: "JVM error report". :)
I'm guessing this is the path you're curious about?
(It's from the Fedora package "rxtx".)
Interestingly, while I haven't personally tested this yet, folks are reporting that the Fedora build of rxtx, when coupled with the Sun JVM, seems to work properly, which suggests that this might actually be a problem with OpenJDK, or at least a point of differentiation between OpenJDK and Sun's release.
I'll try and get a moment to test that personally tonight or tomorrow.
Created attachment 384501 [details]
Sun JVM error log
I stand corrected; Sun's JVM produced the same results, so you're right, it's probably a good idea to reassign to rxtx. Here's the JVM I just tried it on, as downloaded from Sun's website, for reference:
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
I've attached the error log to this message, for comparison.
rxtx-2.2-0.1.20100211.fc12 has been submitted as an update for Fedora 12.
Yep, that fixes it!
I'd also noticed a similar problem connecting to XBees via RXTX, which I assumed was the same issue, and it was; they're now working just fine via the java xbee-api.
rxtx-2.2-0.1.20100211.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update rxtx'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1841
rxtx-2.2-0.1.20100211.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.