[Needs 0.27] xchat-gnome crashed with SIGSEGV in handle_command()

Bug #415586 reported by Tony Espy
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
XChat-GNOME
Fix Released
Critical
xchat-gnome (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: xchat-gnome

xchat-gnome was runnning displayed, however it was idle ( ie. I was using another program at the time ).

I'm running karmic w/the latest updates as of this 10:30 AM EDT.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 18 16:17:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: nvidia wl
Package: xchat-gnome 1:0.26.1-1ubuntu1
ProcCmdline: xchat-gnome
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
 Segfault happened at: 0x4646f0: cmpb $0x0,(%rsi)
 PC (0x004646f0) ok
 source "$0x0" ok
 destination "(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 ?? ()
 ?? ()
 handle_command ()
 inbound_login_start ()
 ?? ()
Title: xchat-gnome crashed with SIGSEGV in handle_command()
Uname: Linux 2.6.31-6-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:irc_set_away (serv=0x205b2e0, reason=0x0) at proto-irc.c:123
cmd_away (sess=0x205bed0,
handle_command (sess=0x205bed0,
inbound_login_start (sess=0x205bed0,
irc_inline (serv=<value optimized out>,

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
Revision history for this message
Pedro Villavicencio (pedro) wrote : Re: xchat-gnome crashed with SIGSEGV in handle_command()

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=592491

Changed in xchat-gnome (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
Changed in xchat-gnome:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Hello Tony is there any chance to attach your xchat config file? it's located at ~/.xchat2 . Thanks in advance.

Changed in xchat-gnome (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Tony Espy (awe) wrote :

Note, the attached file is the default config file, I haven't touched it AFAIK.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

comment from upstream:

"This problem has been fixed in the development version. The fix will be
available in the next major software release. Thank you for your bug report.
Thanks for taking the time to report this bug.

http://git.gnome.org/browse/xchat-gnome/commit/?id=1418579a815af27190b56ac3595ec8bae5b71647"

Changed in xchat-gnome (Ubuntu):
status: Incomplete → Fix Committed
Revision history for this message
Bryce Harrington (bryce) wrote :
visibility: private → public
summary: - xchat-gnome crashed with SIGSEGV in handle_command()
+ [Needs 0.27] xchat-gnome crashed with SIGSEGV in handle_command()
Bryce Harrington (bryce)
Changed in xchat-gnome (Ubuntu):
importance: Medium → High
David Futcher (bobbo)
tags: added: patch-accepted-upstream
Changed in xchat-gnome:
importance: Unknown → Critical
status: New → Fix Released
Bryce Harrington (bryce)
Changed in xchat-gnome (Ubuntu):
status: Fix Committed → Triaged
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I've confirmed that this patch is currently in Natty's xchat-gnome.

Changed in xchat-gnome (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.