| Summary: | [rxtx] eclipse crashes after opening a serial connection via Target Management Terminal | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Dennis.Wassenberg | ||||
| Component: | Terminal | Assignee: | dsdp.tm.core-inbox <tm.core-inbox> | ||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | eclipse, remy.suen | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dennis.Wassenberg
Created attachment 200078 [details]
Error log of the crash
Bugs with TM goes to TM. Apparently it crashes in RXTX native code: 0x00007f76cbc7b0db: <offset 0xa0db> in /IDE/test/eclipse/plugins/gnu.io.rxtx.linux.x86_64_2.1.7.3_v20070717/os/linux/x86_64/librxtxSerial.so There's nothing Java / Eclipse can do when a linked sharedlib crashes in native code. Please try getting an updated RXTX and/or report on the RXTX mailing list: http://rxtx.qbang.org FWIW, an Eclipse plugin hasn't been published yet of any newer RXTX builds but you should be able to grab an rxtx-2.2pre2 and install in your JRE, then remove the RXTX-2.0 plugin from Eclipse and run. If that doesn't help, build RXTX yourself. If that also doesn't help, report to the RXTX mailing list. They'll likely want to know what kind of serial port you have and what OS exactly you're running on. |