glade crashed with SIGSEGV in glade_model_data_column_index()

Bug #916711 reported by David Planella
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glade (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I was just editing a liststore by adding and deleting columns to it in Glade when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: glade 3.10.2-1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 15 09:59:31 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/glade
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110319)
ProcCmdline: glade data/ui/PreferencesQreatorDialog.ui data/ui/AboutQreatorDialog.ui data/ui/QreatorWindow.ui
SegvAnalysis:
 Segfault happened at: 0x7f52e3de6dc5 <glade_model_data_column_index+21>: mov 0x20(%rax),%rbx
 PC (0x7f52e3de6dc5) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: glade
StacktraceTop:
 glade_model_data_column_index () from /usr/lib/glade/modules/libgladegtk.so
 glade_model_data_column_rename () from /usr/lib/glade/modules/libgladegtk.so
 ?? () from /usr/lib/glade/modules/libgladegtk.so
 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
Title: glade crashed with SIGSEGV in glade_model_data_column_index()
UpgradeStatus: Upgraded to precise on 2012-01-09 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
David Planella (dpm) wrote :
visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glade (Ubuntu):
status: New → Confirmed
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.