Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29679 - [eclipse] Crash because of libglib
Attached to Project:
Arch Linux
Opened by Markus (kwinz) - Monday, 30 April 2012, 16:26 GMT
Last edited by Allan McRae (Allan) - Saturday, 17 November 2012, 03:10 GMT
Opened by Markus (kwinz) - Monday, 30 April 2012, 16:26 GMT
Last edited by Allan McRae (Allan) - Saturday, 17 November 2012, 03:10 GMT
|
DetailsDescription:
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f697c78aee5, pid=3074, tid=140091111302912 # # JRE version: 7.0_03-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (22.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x5fee5] g_slice_alloc+0x125 # # 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: # /root/hs_err_pid3074.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # Additional info: eclipse-3.7.2-2 libglib-2.0.so.0.3000.2 Steps to reproduce: happens randomly |
This task depends upon
Comment by Greg (dolby) -
Monday, 15 October 2012, 10:10 GMT
Still a problem with latest version?