xchat crashed with SIGSEGV in g_main_context_dispatch()

Bug #534195 reported by Mario Limonciello
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xchat
New
Undecided
Unassigned
xchat (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: xchat

While closing xchat

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Mar 7 23:52:08 2010
Disassembly: 0x3644d80: Cannot access memory at address 0x3644d80
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/xchat
NonfreeKernelModules: wl
Package: xchat 2.8.6-4ubuntu4
ProcCmdline: xchat
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x3644d80: Cannot access memory at address 0x3644d80
 PC (0x03644d80) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: xchat
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: xchat crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.32-15-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

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

StacktraceTop:
 ?? ()
 dbus_server_setup_with_g_main (server=0x96a0c90,
 g_markup_parse_context_parse () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_node_first_sibling () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xchat (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Andreas Moog (ampelbein) wrote : Steps to reproduce?

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

 status incomplete
 subscribe

visibility: private → public
Changed in xchat (Ubuntu):
status: New → Incomplete
Revision history for this message
Mario Limonciello (superm1) wrote :

All I did was closed Xchat.

I've reproduced it twice.

Changed in xchat (Ubuntu):
status: Incomplete → New
Revision history for this message
Andreas Moog (ampelbein) wrote : Re: [Bug 534195] Re: xchat crashed with SIGSEGV in g_main_context_dispatch()

Thanks. This looks like an upstream issue, so it would be best if
someone having the problem could open a bug report at
https://sourceforge.net/tracker/?group_id=239&atid=100239 .

 tag upstream
 affects ubuntu/xchat
 status confirmed
 affects xchat

Changed in xchat (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
Changed in xchat (Ubuntu):
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.