Community
Participate
Working Groups
Created attachment 223797 [details] log as user root Hello Working environment is: RHEL6.2 64bit Eclipse Indigo Target Management Terminal 3.2.1.R33 RXTX 2.1-7r4 After few seconds of connection to my /dev/pts/xxx (no response) I get: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fd4a50dba6a, pid=19937, tid=140551811659520 # # JRE version: 7.0_04-b20 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.0-b21 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [librxtxSerial.so+0x7a6a] Java_gnu_io_RXTXPort_nativeDrain+0xea # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/noamc/workspace/setup/hs_err_pid19937.log [thread 140551310468864 also had an error] # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # I tried working as user root with same results. Any idea? Thanks
Created attachment 223798 [details] as normal user (non root)
Are you sure that /dev/pts/xxx is a serial port ? It seems like a Pseudoterminal to me, on which nobody might be reading, and that might be triggering an RXTX problem like http://bugzilla.qbang.org/show_bug.cgi?id=199 Now RXTX shouldn't crash no matter what, but maybe it works when you just pick a proper port. On my RHEL6.2 box, serial ports are listed as /dev/ttyS*
Yes it is pseudo terminal and I want to access it. I was pointed to RXTX plugin as one that can be an alternative and keep my work inside eclipse window. Instead of currently using external tool such minicom ("minicom -p /dev/pts/xxx").
So if minicom works, RXTX should work too ... yet I find it a bit odd to use a serial line emulation for accessing a local terminal. Have you considered using a "Local Terminal" launch ? That's optimized for local pty's (the launch will create a fresh pty for you).
I installed Local Terminal from: http://elt.googlecode.com/git/update-site Indeed I cannot configure it connect to my PTY. Therefore this plugin can not help me. What else can be done so that RXTX will work for my case?
Well you can try a more recent version of RXTX, or debug and fix RXTX ... We have successfully used RXTX + TM Serial to connect to PTY's created by socat, this works fine as long as the socat process runs; for a description see http://bugzilla.qbang.org/show_bug.cgi?id=199 so I'm afraid I can't tell why RXTX would crash in your special case... What I can do is post an update on this bug in case I hear about a new release by RXTX that you could try.
The problem was in the librxtxSerial.so file in the gnu.io.rxtx.linux.x86_64 plugin. Once we replaced the so file with the latest version (http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip) it worked fine (although it gives a warning about version mismatch between the java files version and the so version). Will the gnu.io.rxtx.linux.x86_64 plugin be updated once the latest rxtx version is released?
The Terminal component of the Eclipse Ecosystem has a new home. The Terminal is now part of the Eclipse CDT project[1]. This change means a new Git repo[2], P2 site[3] and Bugzilla component. The terminal will continue to be delivered as part of the quarterly Simultaneous Release of Eclipse as well. The marketplace entry[4] had not been updated in a few years. It will once again install the latest release of the terminal on the latest release of the whole IDE (currently 2020-03). If this bug is no longer relevant, please feel free to comment or close the bug. If you can confirm if this issues still occurs in the latest release please do let me know in a comment. [1] https://wiki.eclipse.org/CDT/User/NewIn911 [2] https://git.eclipse.org/c/cdt/org.eclipse.cdt.git (in the terminal directory) [3] current release is 9.11 - P2 site https://download.eclipse.org/tools/cdt/releases/9.11/ [4] https://marketplace.eclipse.org/content/tm-terminal (This comment was added to all open terminal bugs along with changing the Product/component pair to CDT/terminal.)
