Bug 605907 - [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-41.b18.fc13: raise: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-41.b18.fc13: raise: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 602342
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6145a38a28f0c264a8788200da0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-19 10:33 UTC by murali v
Modified: 2010-11-08 18:48 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:48:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (28.88 KB, text/plain)
2010-06-19 10:33 UTC, murali v
no flags Details

Description murali v 2010-06-19 10:33:14 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java -Dmvel.debugger=true -classpath /home/murali/workspace_ee/droolsWorking/bin:/home/murali/drools-5.0-bin/drools-api-5.0.1.jar:/home/murali/drools-5.0-bin/drools-workitems-5.0.1.jar:/home/murali/drools-5.0-bin/drools-transformer-jxls-5.0.1.jar:/home/murali/drools-5.0-bin/drools-transformer-smooks-5.0.1.jar:/home/murali/drools-5.0-bin/lib/h2-1.0.77.jar:/home/murali/drools-5.0-bin/lib/persistence-api-1.0.jar:/home/murali/drools-5.0-bin/lib/slf4j-jdk14-1.5.2.jar:/home/murali/drools-5.0-bin/lib/joda-time-1.6.jar:/home/murali/drools-5.0-bin/lib/ant-1.6.5.jar:/home/murali/drools-5.0-bin/lib/rome-0.9.jar:/home/murali/drools-5.0-bin/lib/xstream-1.3.1.jar:/home/murali/drools-5.0-bin/lib/stax-1.2.0.jar:/home/murali/drools-5.0-bin/lib/antlr-runtime-3.1.1.jar:/home/murali/drools-5.0-bin/lib/janino-2.5.15.jar:/home/murali/drools-5.0-bin/lib/hibernate-commons-annotations-3.1.0.GA.jar:/home/murali/drools-5.0-bin/lib/jaxb-xjc-2.0.3.jar:/home/murali/drools-5.0-bin/lib/mvel2-2.0.10.jar:/home/murali/drools-5.0-bin/lib/jxls-reader-0.9.6.jar:/home/murali/drools-5.0-bin/lib/mail-1.4.jar:/home/murali/drools-5.0-bin/lib/jsr94-1.1.jar:/home/murali/drools-5.0-bin/lib/jaxb-impl-2.0.3.jar:/home/murali/drools-5.0-bin/lib/jxl-2.4.2.jar:/home/murali/drools-5.0-bin/lib/ant-nodeps-1.6.5.jar:/home/murali/drools-5.0-bin/lib/activation-1.1.jar:/home/murali/drools-5.0-bin/lib/jettison-1.0.1.jar:/home/murali/drools-5.0-bin/lib/milyn-smooks-javabean-1.1.jar:/home/murali/drools-5.0-bin/lib/hibernate-core-3.3.0.SP1.jar:/home/murali/drools-5.0-bin/lib/hibernate-entitymanager-3.4.0.GA.jar:/home/murali/drools-5.0-bin/lib/commons-compress-1.0-20080905.032625-1.jar:/home/murali/drools-5.0-bin/lib/smack-3.0.4.jar:/home/murali/drools-5.0-bin/lib/commons-exec-1.0.0-20080905.033237-1.jar:/home/murali/drools-5.0-bin/lib/activemq-core-5.2.0.jar:/home/murali/drools-5.0-bin/lib/commons-net-2.0.jar:/home/murali/drools-5.0-bin/lib/jboss-seam-2.1.1.GA.jar:/home/murali/drools-5.0-bin/lib/commons-collections-3.2.jar:/ho
comment: just tried to debug the projects
component: java-1.6.0-openjdk
crash_function: raise
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
global_uuid: 6145a38a28f0c264a8788200da0538a14d5fee6d
kernel: 2.6.33.5-124.fc13.i686.PAE
package: java-1.6.0-openjdk-1:1.6.0.0-41.b18.fc13
rating: 4
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)

How to reproduce
-----
1. try to debug the projects as drools project
2.
3.

Comment 1 murali v 2010-06-19 10:33:18 UTC
Created attachment 425322 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:48:31 UTC

*** This bug has been marked as a duplicate of bug 602342 ***

Comment 3 Karel Klíč 2010-11-08 18:48:31 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #602342.

Sorry for the inconvenience.


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