[apport] xchat-gnome crashed with SIGSEGV in g_closure_invoke()

Bug #102165 reported by Peter Berry
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
XChat-GNOME
Fix Released
Critical
xchat-gnome (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xchat-gnome

Happened while using the network selection dialogue. Started searching, it reached Freenode, I pressed enter, crash.

ProblemType: Crash
Architecture: amd64
Date: Tue Apr 3 01:32:44 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/xchat-gnome
Package: xchat-gnome 1:0.16-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: xchat-gnome
ProcCwd: /home/pwb
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Uname: Linux rhuidean 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Peter Berry (pwberry) wrote :
Changed in xchat-gnome:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:dialog_response (dialog=0xa72030, response=<value optimized out>, data=<value optimized out>) at connect-dialog.c:76
IA__g_closure_invoke (closure=0x8c0da0, return_value=0x0, n_param_values=2, param_values=0x7fff249ec910, invocation_hint=0x7fff249ec7e0)
signal_emit_unlocked_R (node=0x7570e0, detail=0, instance=0xa72030, emission_return=0x0, instance_and_params=0x7fff249ec910) at gsignal.c:2440
IA__g_signal_emit_valist (instance=0xa72030, signal_id=<value optimized out>, detail=0, var_args=0x7fff249ecb90) at gsignal.c:2199
IA__g_signal_emit (instance=0x2b2589ccb960, signal_id=10945616, detail=33) at gsignal.c:2243

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)?

Changed in xchat-gnome:
status: Unconfirmed → Needs Info
Revision history for this message
Peter Berry (pwberry) wrote :

Right, in more detail here's how to reproduce it:

* Running for the first time. IF you've already run it you can reproduce by removing ~/.xchat2 and ~/.gconf/apps/xchat first.
* Dialogue pops up asking you to enter your nick and real name. Do this, and press OK
* Connects automatically to #ubuntu on "Ubuntu Server"
* Close the connection.
* IRC -> Connect..., press Ctrl-F and type "Free", Freenode is highlighted. Press enter.
* Crash.

Revision history for this message
Peter Berry (pwberry) wrote :

That valgrind log is for i386 btw, where the original bug report was for a crash on amd64, though it's the same hardware (I reinstalled again today).

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

The log show an error, it has no detail though, could you get a new one with xchat-gnome-dbgsym installed?

Revision history for this message
Peter Berry (pwberry) wrote :

I can't seem to get a more useful backtrace than that. Following the instructions at https://wiki.ubuntu.com/DebuggingProgramCrash, I installed xchat-gnome-dbgsym and ran it as before, but it still shows no debug symbols. Doing a dpkg-query -L I found /usr/lib/debug/usr/bin/xchat-gnome, but with that I get the following:

[pwb@rhuidean ~]$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/debug/usr/bin/xchat-gnome
valgrind: m_ume.c: can't open interpreter

Revision history for this message
Peter Berry (pwberry) wrote :

Gah! s/backtrace/valgrind log/

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

you have to run the normal xchat-gnome, the /usr/lib/debug version is only debug symbols which are used automatically

Revision history for this message
Peter Berry (pwberry) wrote :

Sorry for the delay.

Revision history for this message
Peter Berry (pwberry) wrote :

Incidentally I can also make the method to reproduce a bit more straightforward:

1. Make sure one network is set to connect automatically. (Haven't tested with more than one)
2. Start xchat-gnome, let it connect, then close the connection using the context menu on the networks/channels list.
3. Try to connect to a network using IRC -> Connect. Crash.

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

I've opened a bug upstream with those details now: http://bugzilla.gnome.org/show_bug.cgi?id=429920

Changed in xchat-gnome:
status: Needs Info → Confirmed
Changed in xchat-gnome:
status: Unknown → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now

Changed in xchat-gnome:
status: Confirmed → Fix Committed
Changed in xchat-gnome:
status: Confirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version is in gutsy

Changed in xchat-gnome:
status: Fix Committed → Fix Released
Changed in xchat-gnome:
importance: Unknown → Critical
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.