xchat-gnome crashed with SIGSEGV in g_type_check_instance_cast()

Bug #192236 reported by Michael D. Stemle, Jr.
12
Affects Status Importance Assigned to Milestone
libsexy (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xchat-gnome

I was trying to change my nick by clicking on my nick to the left of the text input entry. Upon typing a new nick and hitting the Enter key, crashing ensued.

ProblemType: Crash
Architecture: i386
Date: Fri Feb 15 14:53:31 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: vmnet vmblock vmmon
Package: xchat-gnome 1:0.18-2ubuntu1
PackageArchitecture: i386
ProcCmdline: xchat-gnome --sm-config-prefix /xchat-gnome-yHmIix/ --sm-client-id 117f000101000119869694800000066270002 --screen 0
ProcCwd: /home/manchicken
ProcEnviron:
 PATH=/home/manchicken/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 g_type_check_instance_cast ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: xchat-gnome crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux thepea 2.6.24-7-generic #1 SMP Thu Feb 7 01:29:58 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0xb79197ab <g_type_check_instance_cast+75>: testb $0x40,0x7(%esi)
 PC (0xb79197ab) ok
 source "$0x40" ok
 destination "0x7(%esi)" (0x000f7977) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libgobject-2.0.so.0
?? ()
?? ()
_GLOBAL_OFFSET_TABLE_ ()
?? () from /usr/lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:?? () from /usr/lib/libgobject-2.0.so.0
?? ()
?? ()
_GLOBAL_OFFSET_TABLE_ ()
?? () from /usr/lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Apport retracing service (apport) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in xchat-gnome:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in xchat-gnome:
status: Incomplete → Invalid
Revision history for this message
Juha Siltala (topyli) wrote :

I tried to go /away on all the networks i'm on. xchat-gnome crashed.

Revision history for this message
Juha Siltala (topyli) wrote :

This bug cannot be closed. There is a crasher bug in a program in main, happening in very common use cases.

Changed in xchat-gnome:
status: Invalid → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

there's not a good stacktrace of the issue, so yes the bug can be closed until someone send a good stacktrace. thanks.

Changed in xchat-gnome:
status: New → Invalid
Revision history for this message
Miia Sample (myrtti) wrote :

Attaching valgrind-logs.

Changed in xchat-gnome:
status: Invalid → Confirmed
Revision history for this message
Miia Sample (myrtti) wrote :
Revision history for this message
Miia Sample (myrtti) wrote :

To duplicate the behaviour in the valgrind-log:
* log into several networks
* click your nick on the left side of the entry box
* set yourself away on all networks and change your nick.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue in this log are libsexy ones, the debug packages for this library are not available though which means there is no debug information, reassing there anyway

Changed in xchat-gnome:
assignee: desktop-bugs → nobody
Kees Cook (kees)
description: updated
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

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