Bug 562300 - [abrt] crash in eclipse-platform-1:3.5.1-22.fc12
Summary: [abrt] crash in eclipse-platform-1:3.5.1-22.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d223f13f053ab6539d04c58c3e0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-05 20:54 UTC by don gilbert
Modified: 2010-08-23 19:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-23 19:45:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (97.95 KB, text/plain)
2010-02-05 20:54 UTC, don gilbert 		no flags Details
View All

Description don gilbert 2010-02-05 20:54:18 UTC 
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
executable: /usr/lib/eclipse/eclipse
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: eclipse-platform-1:3.5.1-22.fc12
rating: 3
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.ran periodic software update in background
2.it crashed, Like Firefox & Thunderbird & Yum updater crash
3.
Comment 1 don gilbert 2010-02-05 20:54:20 UTC 
Created attachment 389188 [details]
File: backtrace
Comment 2 Andrew Overholt 2010-02-05 21:02:57 UTC 
Can you please explain a bit more how this happened?  Were you just running Eclipse with PackageKit going in the background and it crashed?  Can you make it happen without PackageKit doing an update?

I need to be able to reproduce the crash to figure out what caused it.  Thanks.
Comment 3 Andrew Overholt 2010-02-08 15:51:09 UTC 
Any update here, Don?
Comment 4 Andrew Overholt 2010-08-23 19:45:24 UTC 
This has been sitting in NEEDINFO for a while.  Please re-open if there are
still problems.
Note You need to log in before you can comment on or make changes to this bug.