XCHAT crashed in g_type_check_instance() after pressing ctrl-i numerous times

Bug #349754 reported by Don Zavitz on 2009-03-27
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xchat
New
Undecided
Unassigned
xchat (Ubuntu)
High
Unassigned

Bug Description

Binary package hint: xchat

xchat crashed with SIGSEGV in g_type_check_instance()

pressing ctrl-i 5-8 times crashes xchat, confirmed from another user in #ubuntu+1

jaunty 9.04 beta fully updated as of today 2.6.28-11-generic amd64

xchat version 2.8.6-2.1ubuntu4

upstream bug: http://sourceforge.net/p/xchat/bugs/1302/

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/xchat
NonfreeKernelModules: nvidia
Package: xchat 2.8.6-2.1ubuntu4
ProcCmdline: xchat
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat
StacktraceTop:
 g_type_check_instance ()
 g_signal_connect_data ()
 ?? ()
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: xchat crashed with SIGSEGV in g_type_check_instance()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Don Zavitz (dzavitz) wrote :

StacktraceTop:IA__g_type_check_instance (type_instance=0x200000000)
IA__g_signal_connect_data (instance=0x200000000,
mg_add_pane_signals (gui=0x1872e00)
IA__g_main_context_dispatch (context=0x10c2890)
g_main_context_iterate (context=0x10c2890, block=1,

Changed in xchat:
importance: Undecided → Medium

I recreated this using xchat version 2.8.6-2.1ubuntu4 on Jaunty. I found it necessary to press the keystroke multiple times quickly to recreate the bug.

visibility: private → public
Changed in xchat (Ubuntu):
status: New → Triaged
Bryce Harrington (bryce) on 2012-02-23
summary: - XCHAT crashed after pressing ctrl-i numerous times
+ XCHAT crashed in g_type_check_instance() after pressing ctrl-i numerous
+ times
Bryce Harrington (bryce) wrote :

[Thread 0xb64a4b40 (LWP 20591) exited]
Still reproducible on Precise

[New Thread 0xb64a4b40 (LWP 20601)]

Program received signal SIGSEGV, Segmentation fault.
0xb79c7e47 in g_type_check_instance ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
(gdb) bt full
#0 0xb79c7e47 in g_type_check_instance ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#1 0xb79bc378 in g_signal_connect_data ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#2 0x0806b017 in ?? ()
No symbol table info available.
#3 0xb75bb520 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0xb75bdaba in g_main_context_dispatch ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0xb75bdec5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0xb75be30b in g_main_loop_run ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#7 0xb7c7bd0f in IA__gtk_main ()
    at /build/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:1329
        tmp_list = <optimized out>
        functions = 0x0
        init = <optimized out>
        loop = 0x81b9678
#8 0x0805f2d8 in ?? ()
No symbol table info available.
#9 0x08054945 in ?? ()
No symbol table info available.
#10 0xb73ec4d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#11 0x08054985 in ?? ()
No symbol table info available.

tags: added: precise
Changed in xchat (Ubuntu):
importance: Medium → High
Bence Lukács (lukacs-bence1) wrote :

+1 Bryce, it is still exist in Precise.

Scott Moser (smoser) wrote :

just for the record, hit 'ctrl-i' twice quickly and saw this on 2.8.8-7.1ubuntu5 (current utopic)
went looking upstream just to check there. it is bug http://sourceforge.net/p/xchat/bugs/1302/ .

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers