Bug 582078 - [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-37.b17.fc12: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-37.b17.fc12: Process /usr/lib/jv...
Keywords:
Status: CLOSED DUPLICATE of bug 540962
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3abacec2b4eb2f6b9f045bc3dad...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-14 03:01 UTC by John 'Warthog9' Hawley
Modified: 2010-05-25 09:56 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:56:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (54.78 KB, text/plain)
2010-04-14 03:01 UTC, John 'Warthog9' Hawley
no flags Details

Description John 'Warthog9' Hawley 2010-04-14 03:01:53 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws -J-Xms32M -J-Xmx40M -Xnofork /home/warthog9/ikvm.jnlp
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-37.b17.fc12
rating: 3
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 John 'Warthog9' Hawley 2010-04-14 03:01:55 UTC
Created attachment 406401 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:56:20 UTC

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

Comment 3 Karel Klíč 2010-05-25 09:56:20 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 #540962.

Sorry for the inconvenience.


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