eclipse crashed with SIGSEGV in gdk_window_enable_synchronized_configure()

Bug #926502 reported by grue
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
New
Undecided
Unassigned

Bug Description

Unsure of what happened, was using eclipse as usual and it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: eclipse-platform 3.7.1-1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 3 20:10:28 2012
ExecutablePath: /usr/lib/eclipse/eclipse
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120122)
ProcCmdline: /usr/lib/eclipse/eclipse
SegvAnalysis:
 Segfault happened at: 0x7ff0a68ce60e <gdk_window_enable_synchronized_configure+14>: mov 0x18(%rdi),%rbx
 PC (0x7ff0a68ce60e) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: eclipse
StacktraceTop:
 gdk_window_enable_synchronized_configure () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: eclipse crashed with SIGSEGV in gdk_window_enable_synchronized_configure()
UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
grue (octarine) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #863469, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.