Bug 920771 - [abrt] java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18: raise: Process /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Summary: [abrt] java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18: raise: Process /usr/lib/jvm/j...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.7.0-openjdk
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b6b48b516a033133fcc7edb38d3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 17:17 UTC by Scott Williams
Modified: 2013-03-12 17:19 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-12 17:19:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (89.16 KB, text/plain)
2013-03-12 17:17 UTC, Scott Williams
no flags Details
File: build_ids (3.40 KB, text/plain)
2013-03-12 17:17 UTC, Scott Williams
no flags Details

Description Scott Williams 2013-03-12 17:17:17 UTC
Version-Release number of selected component:
java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18

Additional info:
backtrace_rating: 3
cmdline:        java -cp /home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/davmail.jar::/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/activation-1.1.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/commons-codec-1.3.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/commons-collections-3.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/commons-httpclient-3.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/commons-logging-1.0.4.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/htmlcleaner-2.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/jackrabbit-webdav-1.4.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/jcharset-1.3.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/jcifs-1.3.14.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/jdom-1.0.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/junit-3.8.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/log4j-1.2.16.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/mail-1.4.3.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/slf4j-api-1.3.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/slf4j-log4j12-1.3.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/stax2-api-3.1.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/stax-api-1.0.1.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/swt-3.7-gtk-linux-x86_64.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/winrun4j-0.4.4.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/woodstox-core-asl-4.1.2.jar:/home/scott/Projects/davmail-linux-x86_64-4.1.0-2042/lib/xercesImpl-2.8.1.jar davmail.DavGateway
core_backtrace: 
crash_function: raise
executable:     /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java
kernel:         3.8.1-201.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 __run_exit_handlers at /lib64/libc.so.6
 #5 exit at /lib64/libc.so.6
 #6 gdk_x_io_error at gdkmain-x11.c:544
 #7 _XIOError at XlibInt.c:1618
 #8 _XEventsQueued at xcb_io.c:365
 #9 XPending at Pending.c:55
 #10 gdk_check_xpending at gdkevents-x11.c:159
 #11 gdk_event_prepare at gdkevents-x11.c:2361
 #12 g_main_context_prepare at gmain.c:2986
 #13 Java_org_eclipse_swt_internal_gtk_OS__1g_1main_1context_1prepare at /home/scott/.swt/lib/linux/x86_64/libswt-pi-gtk-3735.so

Comment 1 Scott Williams 2013-03-12 17:17:20 UTC
Created attachment 709081 [details]
File: backtrace

Comment 2 Scott Williams 2013-03-12 17:17:23 UTC
Created attachment 709082 [details]
File: build_ids

Comment 3 Deepak Bhole 2013-03-12 17:19:58 UTC
This error originated in JNI code from /home/scott/.swt/lib/linux/x86_64/libswt-pi-gtk-3735.so 

There is nothing that the JDK can do to address this. Please contact the vendor of the above file to fix it.


Note You need to log in before you can comment on or make changes to this bug.