abrt detected a crash. How to reproduce ----- 1. 2. 3. Comment ----- Tried to open (or add) an SVN repository in the repository explorer Additional information ====== Attached files ---- backtrace Attached files ---- cmdline component ----- java-1.6.0-openjdk executable ----- /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java kernel ----- 2.6.31.5-96.fc12.x86_64 package ----- java-1.6.0-openjdk-1:1.6.0.0-31.b16.fc12 reason ----- Process was terminated by signal 6
Created attachment 367436 [details] File: backtrace
Does installing debuginfo package with: yum install --enablerepo=fedora-debuginfo -y java-1.6.0-openjdk-debuginfo make the output any more verbose?
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 539510 has been marked as a duplicate of this bug. ***
Created attachment 372479 [details] Error Log produced by JVM This error log is created by the JVM after saying: [philippe@courier ~]$ eclipse # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000003511c7772e, pid=2421, tid=140001083156240 # # JRE version: 6.0-b16 # Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 ) # Distribution: Custom build (Thu Nov 12 09:47:56 EST 2009) # Problematic frame: # C [libc.so.6+0x7772e] # # An error report file with more information is saved as: # /home/philippe/hs_err_pid2421.log
Created attachment 372480 [details] Backtrace (added in comments)
Tried it again, after installing the debuginfo package ... I removed my .eclipse folder, my workspace folder and started eclipse. I chose the default workspace, closed the "welcome" screen and clicked on window -> show view -> other -> SVN -> SVN repository. Next, I right clicked, chose new repository location and added my SVN repository (HTTPS link, uses a self signed cert). Next, a waiting window appears, which is about the time when an error report shows up in the console (see attachments). I've attached the error log and a backtrace ... Philippe
After messing around with it, I have SVN working with the SVNkit client. The JavaHL (native) client is the one giving problems ... Philippe
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.