| Summary: | [abrt] java-1.6.0-openjdk-1.6.0.0-60.1.10.4.fc15: __GI_raise: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kent Bair <fuzzybair> | ||||||||
| Component: | eclipse | Assignee: | Alexander Kurtakov <akurtako> | ||||||||
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | ahughes, akurtako, andjrobins, dbhole, jon.vanalten, jvanek, lkundrak, mjw, mmatejov, omajid, overholt, rgrunber, sgehwolf, swagiaal | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:06d6fc6dbe1016dce712163f9ccf68e73265a611 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-12-30 15:05:51 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Kent Bair
2011-12-22 01:13:51 UTC
Created attachment 549107 [details]
File: dso_list
Created attachment 549108 [details]
File: maps
Created attachment 549109 [details]
File: backtrace
Native SWT library issue originating here: #7 0x00007f1c65421ad1 in Java_org_eclipse_swt_internal_gtk_OS__1g_1object_1get_1qdata () from /usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/114/1/.cp/libswt-pi-gtk-3659.so Re-assigning to Eclipse. Does this happen all the time, Kent? It'll be very difficult if not impossible to fix this without a reproducible test case. no it happened a few times while i was configuring the android sdk after i got that working properly and the needed packages installed it started working properly again. my thoughts is that it had some weird side effects between different dependencies. so unless you see others like it probably not an issue and at any rate a low priority issue. Thanks for the additional info, Kent. Please do re-open if this persists. |