xchat-gnome crashed with SIGSEGV in g_slist_remove()

Bug #444175 reported by Michael DePaulo
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xchat-gnome (Ubuntu)
Triaged
High
Unassigned

Bug Description

Binary package hint: xchat-gnome

I went to join channel #reactos on the ubuntu/freenode IRC server, when it started scrolling through the history of #ubuntu like crazy. It then crashed.

ProblemType: Crash
Architecture: amd64
Date: Mon Oct 5 21:18:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: nvidia
Package: xchat-gnome 1:0.26.1-1ubuntu1
ProcCmdline: xchat-gnome
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x7ff4674abb90 <g_slist_remove+16>: cmp %rsi,(%rax)
 PC (0x7ff4674abb90) ok
 source "%rsi" ok
 destination "(%rax)" (0x206f742073726573) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 g_slist_remove () from /lib/libglib-2.0.so.0
 gtk_tree_row_reference_free ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: xchat-gnome crashed with SIGSEGV in g_slist_remove()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Michael DePaulo (mikedep333) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_slist_remove () from /lib/libglib-2.0.so.0
IA__gtk_tree_row_reference_free (
selection_changed (selection=0x11cd780,
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0

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