Bug 684155 - [abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
Summary: [abrt] eclipse-platform-1:3.6.1-6.1.fc14: Process /usr/lib/eclipse/eclipse wa...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8813f86e4ca790f1bd4ad21ec29...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 10:32 UTC by Manuel
Modified: 2011-03-30 07:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-30 07:24:06 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (115.21 KB, text/plain)
2011-03-11 10:32 UTC, Manuel 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Manuel 2011-03-11 10:32:45 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 117979 bytes
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
Attached file: coredump, 320569344 bytes
executable: /usr/lib/eclipse/eclipse
kernel: 2.6.35.11-83.fc14.i686
package: eclipse-platform-1:3.6.1-6.1.fc14
rating: 3
reason: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299832532
uid: 500

How to reproduce
-----
1.Install eclipse plugins.
2.Run eclipse.
3.
Comment 1 Manuel 2011-03-11 10:32:48 UTC 
Created attachment 483680 [details]
File: backtrace
Comment 2 Alexander Kurtakov 2011-03-14 11:19:04 UTC 
Can you reproduce?
Can you try moving ~/.eclipse to anothre place and see whether it's reproducible?
Was this the first time you started Eclipse from Fedora packages?
Any other info you think we can use?
Comment 3 Alexander Kurtakov 2011-03-30 07:24:06 UTC 
More than 2 weeks without response. Closing the bug.
Please reopen when/if you are ready to spend some time helping us finding your issue.
Note You need to log in before you can comment on or make changes to this bug.