Bug 635881 – xchat-gnome-0.26.1: g_list_length: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 635881 - xchat-gnome-0.26.1: g_list_length: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)


Summary:	xchat-gnome-0.26.1: g_list_length: Process /usr/bin/xchat-gnome was killed by...


Status:	RESOLVED WONTFIX

Product:	xchat-gnome
Classification:	Other
Component:	general
Version:	0.26.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	.30
Assigned To:	xchat-gnome maintainers
QA Contact:	xchat-gnome maintainers

URL:
Whiteboard:	gnome[unmaintained]

Depends on:
Blocks:

Reported:	2010-11-26 21:43 UTC by Brian Pepple
Modified:	2019-02-23 02:49 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Backtrace (22.33 KB, text/plain) 2010-11-26 21:43 UTC, Brian Pepple	Details

Description Brian Pepple 2010-11-26 21:43:39 UTC

Created attachment 175324 [details]
Backtrace

abrt version: 1.1.10
architecture: x86_64
Attached file: backtrace
cmdline: xchat-gnome
component: xchat-gnome
crash_function: g_list_length
executable: /usr/bin/xchat-gnome
kernel: 2.6.35.1-4.rc1.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 (Branched)
How to reproduce: tab tab tab boom
time: 1281296195
uid: 500

Original Bug: https://bugzilla.redhat.com/show_bug.cgi?id=622302

Comment 1 Fabio Durán Verdugo 2010-11-26 23:30:28 UTC

paste here the attach backtrace


Core was generated by `xchat-gnome'.
Program terminated with signal 11, Segmentation fault.

+ Trace 224862

Thread 1 (Thread 4427)

#0 g_list_length
at glist.c line 886
#1 tab_complete_nickname
at text-entry.c line 544
#2 text_entry_tab_complete
at text-entry.c line 357
#3 text_entry_key_press
at text-entry.c line 220
#4 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 86
#5 g_closure_invoke
at gclosure.c line 766
#6 signal_emit_unlocked_R
at gsignal.c line 3322
#7 g_signal_emit_valist
at gsignal.c line 2993
#8 g_signal_emit
at gsignal.c line 3040
#9 gtk_widget_event_internal
at gtkwidget.c line 4988
#10 IA__gtk_window_propagate_key_event
at gtkwindow.c line 5199
#11 gtk_window_key_press_event
at gtkwindow.c line 5229
#12 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 86
#13 g_closure_invoke
at gclosure.c line 766
#14 signal_emit_unlocked_R
at gsignal.c line 3290
#15 g_signal_emit_valist
at gsignal.c line 2993
#16 g_signal_emit
at gsignal.c line 3040
#17 gtk_widget_event_internal
at gtkwidget.c line 4988
#18 IA__gtk_propagate_event
at gtkmain.c line 2434
#19 IA__gtk_main_do_event
at gtkmain.c line 1665
#20 gdk_event_dispatch
at gdkevents-x11.c line 2377
#21 g_main_dispatch
at gmain.c line 2119
#22 g_main_context_dispatch
at gmain.c line 2672
#23 g_main_context_iterate
at gmain.c line 2750
#24 g_main_loop_run
at gmain.c line 2958
#25 IA__gtk_main
at gtkmain.c line 1237
#26 fe_main
at fe-gnome.c line 185
#27 main
at xchat.c line 1065

Comment 2 Ritesh Khadgaray ( irc:ritz) 2011-11-09 18:28:47 UTC

interesting bug report, I have finally disabled optimization rebuilt x-g, and caught this bug.


488			/* more than one match - print a list of options
(gdb) p text_entry->priv->command_completion->cache
$20 = 0x7fffe0013080 = {0x48ce93}
(gdb) p *options
Cannot access memory at address 0xffffffffe0013080

hmmm, this might be x64 specific issue.

Comment 3 André Klapper 2019-02-23 02:49:30 UTC

xchat-gnome is not under active development anymore.
Its codebase has been archived:
https://gitlab.gnome.org/Archive/xchat-gnome/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather reactivate the project
to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the
responsibility for active development again.
You may want to switch to Hexchat (or another IRC client that suits you).