Bug 675197 - [abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib64/eclipse/eclipse was killed by signal 8 (SIGFPE)
[abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib64/eclipse/eclipse ...
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Alexander Kurtakov
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-02-04 10:34 EST by Erwan Legrand
Modified: 2011-02-04 13:36 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-02-04 13:36:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Erwan Legrand 2011-02-04 10:34:02 EST
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/eclipse/eclipse
component: eclipse
executable: /usr/lib64/eclipse/eclipse
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
Comment 1 Erwan Legrand 2011-02-04 10:34:06 EST
Created attachment 477049 [details]
File: backtrace
Comment 2 Andrew Overholt 2011-02-04 11:09:31 EST
Does this happen all the time?  I can't reproduce it here.
Comment 3 Erwan Legrand 2011-02-04 13:28:53 EST

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 13:36:02 EST
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.