Bug 725270 - [abrt] java-1.6.0-openjdk-1:1.6.0.0-53.1.9.8.fc14: __libc_message: 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-53.1.9.8.fc14: __libc_message: Process /u...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e91ea8a5c1601b6190bf948cfc6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-24 22:37 UTC by Daniel S Spicer
Modified: 2011-07-25 14:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-25 14:22:46 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (128.82 KB, text/plain)
2011-07-24 22:37 UTC, Daniel S Spicer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Daniel S Spicer 2011-07-24 22:37:14 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 131911 bytes
cmdline: java -jar /opt/intel/Compiler/11.1/072/idb/gui/intel64/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar -showsplash -gui -gdb ../flowdir_OMP2/flo3d
component: java-1.6.0-openjdk
Attached file: coredump, 658366464 bytes
crash_function: __libc_message
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java
kernel: 2.6.35.13-92.fc14.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-53.1.9.8.fc14
rating: 4
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 14 (Laughlin)
time: 1311546744
uid: 7001

How to reproduce
-----
1.trying to set a breakpoint with Intel's idb debugger
2.
3.
Comment 1 Daniel S Spicer 2011-07-24 22:37:17 UTC 
Created attachment 514936 [details]
File: backtrace
Comment 2 Deepak Bhole 2011-07-25 14:22:46 UTC 
According to the trace, the crash originated in idb code. This bug needs to be opened with them.
Note You need to log in before you can comment on or make changes to this bug.