Bug 675197 - [abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib64/eclipse/eclipse was killed by signal 8 (SIGFPE)
Summary: [abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib64/eclipse/eclipse ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6e01c333aa8875320b9d397a6c5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-04 15:34 UTC by Erwan Legrand
Modified: 2011-02-04 18:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-04 18:36:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (43.10 KB, text/plain)
2011-02-04 15:34 UTC, Erwan Legrand 		no flags Details
View All

Description Erwan Legrand 2011-02-04 15:34:02 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/eclipse/eclipse
component: eclipse
executable: /usr/lib64/eclipse/eclipse
kernel: 2.6.35.10-74.fc14.x86_64
package: eclipse-platform-1:3.6.1-6.1.fc14
reason: Process /usr/lib64/eclipse/eclipse was killed by signal 8 (SIGFPE)
release: Fedora release 14 (Laughlin)
time: 1296739637
uid: 500

How to reproduce
-----
1. Maximize C editor in Eclipse CDT
2.
3.
Comment 1 Erwan Legrand 2011-02-04 15:34:06 UTC 
Created attachment 477049 [details]
File: backtrace
Comment 2 Andrew Overholt 2011-02-04 16:09:31 UTC 
Does this happen all the time?  I can't reproduce it here.
Comment 3 Erwan Legrand 2011-02-04 18:28:53 UTC 
Andrew,

No, this does not happen all the time. Actually this was the first occurrence and it remains the only one so far.
Comment 4 Andrew Overholt 2011-02-04 18:36:02 UTC 
Hmm.  I'm sure you know that it's impossible for us to track it down if we can't reproduce it and the stack trace doesn't give me much information.  I'll close this for now but if it happens again can you please re-open this?  Thanks, Erwan.
Note You need to log in before you can comment on or make changes to this bug.