meld crashed with SIGSEGV in gdk_window_process_updates()

Bug #408273 reported by Niels Egberts
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
meld (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: meld

I was trying to load in 2 files for the first time I tried Meld and it crashed.

ProblemType: Crash
Architecture: amd64
Date: Mon Aug 3 10:55:40 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/meld
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: meld 1.3.0-1
PackageArchitecture: all
ProcCmdline: python /usr/bin/meld
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x7ff3b9572118: mov 0x0(%rbp),%rbx
 PC (0x7ff3b9572118) ok
 source "0x0(%rbp)" (0x00000039) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: meld
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 gdk_window_process_updates ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: meld crashed with SIGSEGV in gdk_window_process_updates()
Uname: Linux 2.6.31-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Niels Egberts (nielsegberts) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_gdk_window_process_updates_recurse (window=0x2db4be0,
_gdk_window_process_updates_recurse (
gdk_window_process_updates_internal (
IA__gdk_window_process_updates (window=0x29a6740,
gtk_window_check_resize (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in meld (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.