Bug 752006

Summary: [abrt] xchat-gnome-0.26.1-14.fc14: g_list_length: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Niranjan Mallapadi Raghavender <mniranja>
Component: xchat-gnomeAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: notting, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:54ef62bf11ea30d5231137657e967762a9b5ded7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 14:20:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Niranjan Mallapadi Raghavender 2011-11-08 10:04:32 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 23730 bytes
cmdline: xchat-gnome
component: xchat-gnome
Attached file: coredump, 44941312 bytes
crash_function: g_list_length
executable: /usr/bin/xchat-gnome
kernel: 2.6.35.14-103.fc14.x86_64
package: xchat-gnome-0.26.1-14.fc14
rating: 4
reason: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1320746212
uid: 500

How to reproduce
-----
1.Not sure, But crashed when closing the xchat-gnome session
2.
3.
Comment 1 Niranjan Mallapadi Raghavender 2011-11-08 10:04:35 UTC 
Created attachment 532257 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 14:20:25 UTC 
Backtrace analysis found this bug to be similar to bug #622302, closing as duplicate.

Bugs which were found to be similar to this bug: 
  0xFFFF: bug #664685, bug #677987
  xchat-gnome: bug #622302, bug #657624, bug #690061, bug #709096, bug #770752

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 622302 ***