Bug 547564

Summary: [abrt] crash in eclipse-platform-1:3.5.1-20.fc12
Product: [Fedora] Fedora Reporter: Mads Kiilerich <mads>
Component: eclipseAssignee: Andrew Overholt <overholt>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: akurtako, oliver, overholt, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:725d689954f06f61883226be9812dea1dc3f34cb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-15 16:55:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mads Kiilerich 2009-12-14 23:14:33 UTC 
abrt 1.0.1 detected a crash.

How to reproduce
-----
X was hanging (while I was investigating bug 547557), so I kill-9'ed it.

Comment
-----
Eclipse had to die, but it shouldn't happen with a sig11 crash.

However, perhaps related to bug 547557

Attached file: backtrace
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
executable: /usr/lib/eclipse/eclipse
kernel: 2.6.31.6-166.fc12.i686.PAE
package: eclipse-platform-1:3.5.1-20.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 Mads Kiilerich 2009-12-14 23:14:35 UTC 
Created attachment 378385 [details]
File: backtrace
Comment 2 Andrew Overholt 2009-12-15 15:18:22 UTC 
Can you send me details on how to reproduce this, please, Mads?
Comment 3 Mads Kiilerich 2009-12-15 15:41:13 UTC 
No, sorry, I can't reproduce it. Perhaps the crash was related to the way X was hanging, or perhaps it was caused by some timing issues after I killed the Xorg process. 

I guess the only hope is that the stacktrace can give a hint where some check is missing, but it seems like the stacktrace is very incomplete?
Comment 4 Andrew Overholt 2009-12-15 15:47:17 UTC 
Yeah, it will be difficult to fix with the small stacktrace and no way to reproduce :(
Comment 5 Mads Kiilerich 2009-12-15 16:55:01 UTC 
Ok, then we close it and assume that the problem either comes back or don't ,-)