Bug 625208 - [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13: raise: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13: raise: Process /usr/lib/jvm/...
Keywords:
Status: CLOSED DUPLICATE of bug 560232
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:045f7e0854b084c79a6bcb033da...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-18 21:10 UTC by Adam Goode
Modified: 2010-08-19 16:02 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-19 16:00:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (65.88 KB, text/plain)
2010-08-18 21:10 UTC, Adam Goode 		no flags Details
View All

Description Adam Goode 2010-08-18 21:10:15 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: java -Xmx512m -jar ij.jar
comment: Ran auto-updater in ImageJ.
component: java-1.6.0-openjdk
crash_function: raise
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java
kernel: 2.6.33.6-147.fc13.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13
rating: 3
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282165559
uid: 9727
Comment 1 Adam Goode 2010-08-18 21:10:18 UTC 
Created an attachment (id=439512)
File: backtrace
Comment 2 Deepak Bhole 2010-08-19 15:28:09 UTC 
Is this error consistently reproducible?
Comment 3 Omair Majid 2010-08-19 16:00:17 UTC 

*** This bug has been marked as a duplicate of bug 560232 ***
Comment 4 Adam Goode 2010-08-19 16:01:20 UTC 
Only saw it once.
Comment 5 Adam Goode 2010-08-19 16:02:45 UTC 
Ah yes, the auto-updater in ImageJ replaces its running jar. So I guess this bug is known.
Note You need to log in before you can comment on or make changes to this bug.