Hide Forgot
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: java -cp /home/CoSustenta/davmail-3_8/davmail.jar::/home/CoSustenta/davmail-3_8/lib/activation-1.1.jar:/home/CoSustenta/davmail-3_8/lib/commons-codec-1.3.jar:/home/CoSustenta/davmail-3_8/lib/commons-collections-3.1.jar:/home/CoSustenta/davmail-3_8/lib/commons-httpclient-3.1.jar:/home/CoSustenta/davmail-3_8/lib/commons-logging-1.0.4.jar:/home/CoSustenta/davmail-3_8/lib/htmlcleaner-2.1.jar:/home/CoSustenta/davmail-3_8/lib/jackrabbit-webdav-1.4.jar:/home/CoSustenta/davmail-3_8/lib/jcifs-1.3.14.jar:/home/CoSustenta/davmail-3_8/lib/jdom-1.0.jar:/home/CoSustenta/davmail-3_8/lib/junit-3.8.1.jar:/home/CoSustenta/davmail-3_8/lib/log4j-1.2.15.jar:/home/CoSustenta/davmail-3_8/lib/mail-1.4.1.jar:/home/CoSustenta/davmail-3_8/lib/slf4j-api-1.3.1.jar:/home/CoSustenta/davmail-3_8/lib/slf4j-log4j12-1.3.1.jar:/home/CoSustenta/davmail-3_8/lib/stax-api-1.0.1.jar:/home/CoSustenta/davmail-3_8/lib/swt-3.6-gtk-linux-x86.jar:/home/CoSustenta/davmail-3_8/lib/wstx-asl-3.2.7.jar:/home/CoSustenta/davmail-3_8/lib/xercesImpl-2.8.1.jar davmail.DavGateway component: java-1.6.0-openjdk crash_function: __gnu_cxx::__verbose_terminate_handler() executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java kernel: 2.6.34.8-68.fc13.i686 package: java-1.6.0-openjdk-1:1.6.0.0-50.1.8.7.fc13 rating: 3 reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1301453408 uid: 500 How to reproduce ----- 1. Using Davmail for an exchange account through Thunderbird, the account could not be read. 2. It crashed after I closed Davmail, but it was not working before my action. It ocurrs regularly. 3.
Created attachment 488620 [details] File: backtrace
Hi. It would be very nice if you could also attach the hs_err_pid* file that should be produced by the crash. Since it happens regularly, could you also attach 1-2 more stack traces? I'm seeing something interesting in this one, and I wonder if it's in the other ones too.
(In reply to comment #2) > Hi. > > It would be very nice if you could also attach the hs_err_pid* file that should > be produced by the crash. > > Since it happens regularly, could you also attach 1-2 more stack traces? I'm > seeing something interesting in this one, and I wonder if it's in the other > ones too. Hello. I cannot find any hs_err_pid file on my computer. Sorry.
(In reply to comment #3) > (In reply to comment #2) > > Hi. > > > > It would be very nice if you could also attach the hs_err_pid* file that should > > be produced by the crash. > > > > Since it happens regularly, could you also attach 1-2 more stack traces? I'm > > seeing something interesting in this one, and I wonder if it's in the other > > ones too. > > Hello. I cannot find any hs_err_pid file on my computer. Sorry. I have found where the log files are saved. I attach the last four crashes' logs in another bug report (I guess this would be a duplicate). Greetings.
This is the other bug report: https://bugzilla.redhat.com/show_bug.cgi?id=684589.
*** This bug has been marked as a duplicate of bug 684589 ***