Bug 601727 - [abrt] crash in eclipse-platform-1:3.5.1-22.fc12: raise: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
[abrt] crash in eclipse-platform-1:3.5.1-22.fc12: raise: Process /usr/lib/ecl...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Andrew Overholt
Fedora Extras Quality Assurance
abrt_hash:4c4a36fc945c7f40eb910ce1ac2...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-08 10:16 EDT by smesquita
Modified: 2010-08-24 07:21 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-24 07:21:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (124.95 KB, text/plain)
2010-06-08 10:16 EDT, smesquita
no flags Details

  None (edit)
Description smesquita 2010-06-08 10:16:45 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
crash_function: raise
executable: /usr/lib/eclipse/eclipse
global_uuid: 4c4a36fc945c7f40eb910ce1ac23e34ed362c712
kernel: 2.6.32.12-115.fc12.i686
package: eclipse-platform-1:3.5.1-22.fc12
rating: 3
reason: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 smesquita 2010-06-08 10:16:49 EDT
Created attachment 422219 [details]
File: backtrace
Comment 2 Andrew Overholt 2010-06-08 10:28:18 EDT
What were you doing when this happened?  Can you make it happen again or was it a one time thing?
Comment 3 smesquita 2010-06-08 10:45:30 EDT
I wasn't doing anything special. It's just crash :(
And yes. It was a one time thing.
Comment 4 Andrew Overholt 2010-08-23 15:31:51 EDT
Should we close this since it's not repeatable?
Comment 5 smesquita 2010-08-24 07:21:18 EDT
(In reply to comment #4)
> Should we close this since it's not repeatable?

Closed.

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