You are not logged in.

#1 2003-07-06 01:45:30

deepfreeze
Member
From: NJ
Registered: 2002-12-27
Posts: 86

xchat segfaults

I just upgraded to the latest version of xchat that is in the repositories via pacman and now it segfaults when attempting to open.  Never had this problem with xchat before...any ideas why now this would happen?


My hovercraft is full of eels.

Offline

#2 2003-07-06 01:57:45

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: xchat segfaults

No, but we had one other person mention that.  I've had no problems with mine.

Maybe it's a stale file somewhere?


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#3 2003-07-06 11:47:25

Gyroplast
Member
From: Germany
Registered: 2002-09-03
Posts: 166
Website

Re: xchat segfaults

Maybe you could strace xchat and see where and why it segfaults? That might point to the stale file Xentac is referring to. And PLEASE don't just delete everything, but rather move suspicious stuff to a safe location to reproduce the bug later if possible, okay? smile

Greets,
  Dennis


"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert

Offline

#4 2003-07-06 20:29:29

deepfreeze
Member
From: NJ
Registered: 2002-12-27
Posts: 86

Re: xchat segfaults

Okay I have run strace on xchat.  Considering I am not a coder and my debugging skills are seriously lacking, I will post the output of the strace with the hope that someone here will assist me in deciphering it:

--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Previous to this segfault was a large amount of read/write commands similar to this (these are actually the 5 lines immediately preceeding the above code:

write(3, "246008D11", 24) = 24
read(3, "1 34171241"..., 32) = 32
read(3, "1300", 4)                = 4
write(3, "(4105300018", 16) = 16
read(3, "113517377377377377"..., 32) = 32

I'm more than willing to continue hunting this down, but I feel like I'm seriously lacking in knowledge about debugging like this...so any help is appreciated smile


My hovercraft is full of eels.

Offline

#5 2003-07-06 20:38:16

Gyroplast
Member
From: Germany
Registered: 2002-09-03
Posts: 166
Website

Re: xchat segfaults

Okay, that alone doesn't quite help. Could you pipe the strace output into a file and upload this file somewhere? Something along the lines of

strace xchat 1>&2 2>strace.log

will do the trick.

Greets,
  Dennis


"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert

Offline

#6 2003-07-07 01:11:39

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: xchat segfaults

Just as a note, 'strace -o file command' works just as well, if not better.


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#7 2003-07-07 02:53:30

deepfreeze
Member
From: NJ
Registered: 2002-12-27
Posts: 86

Re: xchat segfaults


My hovercraft is full of eels.

Offline

#8 2003-07-07 05:54:25

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: xchat segfaults

Hmmm... what's the .icons stuff? (it's a long shot...)  I don't have a .icons directory.  Are you using a special gtk2 theme or a gnome theme or something?


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#9 2003-07-07 09:21:57

Gyroplast
Member
From: Germany
Registered: 2002-09-03
Posts: 166
Website

Re: xchat segfaults

I don't think the themed cursor is the cause of the segfault, the file descriptor of the theme file (4) is close()d a good while before the actual crash. All those reads and writes are done to a socket, opened waaaaay up in the log, so my personal long shot would be bogus communications, although I'd be surprised how that'd cause a segfault. But then I'm not an experienced debugger, either, just good at guessing. *shrug*

It furthermore seems as if xchat segfaults before even displaying the server list, or maybe the server list is switched off altogether. Could you move your .xchat{2} directory out of the way and reinstall xchat, just to make sure there's no configuration issue?

Hey, does it dump a core? Maybe the source can help us, if everything else fails.

Greets,
  Dennis


"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert

Offline

#10 2003-07-08 23:25:23

jlvsimoes
Member
From: portugal
Registered: 2002-12-23
Posts: 392
Website

Re: xchat segfaults

got misself the exact same problem and it do manage to see the server list
and if i dont use tranparent backgrouds it does not segfault


-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------

Offline

#11 2003-07-09 02:30:48

deepfreeze
Member
From: NJ
Registered: 2002-12-27
Posts: 86

Re: xchat segfaults

thanks for the tip...that fixes the problem. In the xchat.conf file, changing the following line allows me to use the program without segfaulting...

text_transparent = 0

however I still think the issue is: why would having a transparent background cause a segfault in the first place? hehe...oh well, at least it is usable now...thanks all for your help!  big_smile


My hovercraft is full of eels.

Offline

#12 2003-07-09 04:36:02

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: xchat segfaults

If you set it back (through the config menus), does it continue to segfault?


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#13 2003-07-10 00:28:30

jlvsimoes
Member
From: portugal
Registered: 2002-12-23
Posts: 392
Website

Re: xchat segfaults

in my case yes it does it works the 1 first time and them if i recall xchat e see the server list and them it segfaults again


-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------

Offline

#14 2003-07-10 09:00:07

Gyroplast
Member
From: Germany
Registered: 2002-09-03
Posts: 166
Website

Re: xchat segfaults

Did anyone with this problem try the CVS version of xchat to see if that's a fixed bug? If not, could you do it and report the bug to the xchat developers if it persists? I suppose they'll be happy to hear about this problem, or at least will be able to pinpoint the culprit better than most of us, if it's not xchat's fault.

xchat works for me, BTW.

Thanks,
  Dennis


"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert

Offline

#15 2003-07-12 12:33:53

dariball
Member
From: Germany - Frankfurt
Registered: 2002-10-20
Posts: 118
Website

Re: xchat segfaults

for me it works too if anyone cares


nothing,
maybe I have a perfect signature _someday_

Offline

#16 2003-07-20 02:32:48

jlvsimoes
Member
From: portugal
Registered: 2002-12-23
Posts: 392
Website

Re: xchat segfaults

i did this
gdb xchat
then run
then it segfault and i typed bt
this is th result
gdb xchat
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/xchat
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x08075302 in gtk_widget_grab_focus ()
(gdb) bt
#0  0x08075302 in gtk_widget_grab_focus ()
#1  0x00000000 in ?? ()

can you do the same to see if we got the same error
btw i send a copy to zed@xchat.org


-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------

Offline

#17 2003-07-20 21:49:07

jlvsimoes
Member
From: portugal
Registered: 2002-12-23
Posts: 392
Website

Re: xchat segfaults

compile it from source not using the makepkg and the debug is this
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/xchat

Program received signal SIGSEGV, Segmentation fault.
0x080752e2 in shade_pixmap_mmx (xtext=0x81de650, p=23068709, x=-1, y=-1,
    w=106, h=1) at xtext.c:2897
2897            Display *xdisplay = GDK_WINDOW_XDISPLAY (xtext->draw_buf);
(gdb) bt
#0  0x080752e2 in shade_pixmap_mmx (xtext=0x81de650, p=23068709, x=-1, y=-1,
    w=106, h=1) at xtext.c:2897
#1  0x08075ba6 in gtk_xtext_load_trans (xtext=0x81de650) at xtext.c:3190
#2  0x08071f2a in gtk_xtext_realize (widget=0x81de650) at xtext.c:916
#3  0x4039cf01 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#4  0x4038af67 in g_type_class_meta_marshal ()
   from /usr/lib/libgobject-2.0.so.0
#5  0x4038ac10 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6  0x4039c34d in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0
#7  0x4039bae0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#8  0x4039bd24 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9  0x401ce4da in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x080762d2 in gtk_xtext_set_font (xtext=0x80ed058, name=0x0)
    at xtext.c:3505
#11 0x08063e24 in mg_update_xtext (wid=0x81de650) at maingui.c:1675
#12 0x08063f5c in mg_create_textarea (gui=0x80ab260, box=0x0) at maingui.c:1708
#13 0x08064442 in mg_create_center (sess=0x81d8cf8, gui=0x80ab260,
    box=0x81dacb0) at maingui.c:1820
#14 0x08064f65 in mg_create_irctab (sess=0x81d8cf8, book=0x0) at maingui.c:2125
#15 0x0806526e in mg_create_tabwindow (sess=0x81d8cf8) at maingui.c:2220
#16 0x08065a8d in mg_changui_new (sess=0x81d8cf8, res=0x81d6db8, tab=1)
    at maingui.c:2483
---Type <return> to continue, or q <return> to quit---
#17 0x08058557 in fe_new_window (sess=0x81de650) at fe-gtk.c:303
#18 0x08090365 in new_session (serv=0x0, from=0x81d8cf8 "021035b", type=0)
    at xchat.c:260
#19 0x08090624 in new_ircwindow (serv=0x1, name=0x0, type=0) at xchat.c:329
#20 0x0808aa54 in servlist_connect (sess=0x0, net=0x1) at servlist.c:490
#21 0x08069400 in servlist_connect_cb (button=0x8103780, userdata=0x0)
    at servlistgui.c:568
#22 0x4039cf01 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#23 0x4038ac10 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#24 0x4039ca6c in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0
#25 0x4039bae0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#26 0x4039bd24 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#27 0x4006c1d7 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x4006d16b in gtk_button_get_relief () from /usr/lib/libgtk-x11-2.0.so.0
#29 0x4039cf01 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#30 0x4038af67 in g_type_class_meta_marshal ()
   from /usr/lib/libgobject-2.0.so.0
#31 0x4038ac10 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#32 0x4039c34d in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0
#33 0x4039bae0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#34 0x4039bd24 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#35 0x4006c127 in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0
#36 0x4006cfeb in gtk_button_get_relief () from /usr/lib/libgtk-x11-2.0.so.0
#37 0x400f2b82 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#38 0x4038af67 in g_type_class_meta_marshal ()
   from /usr/lib/libgobject-2.0.so.0
#39 0x4038ac10 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#40 0x4039c52c in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0
#41 0x4039b8c3 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#42 0x4039bd24 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#43 0x401d04ed in gtk_widget_send_expose () from /usr/lib/libgtk-x11-2.0.so.0
#44 0x400f2957 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#45 0x400f16b6 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#46 0x402a5555 in gdk_add_client_message_filter ()
   from /usr/lib/libgdk-x11-2.0.so.0
#47 0x404c4f6d in g_main_dispatch () from /usr/lib/libglib-2.0.so.0
#48 0x404c5f68 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#49 0x404c627b in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#50 0x404c695f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#51 0x400f0edf in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#52 0x080584bb in fe_main () at fe-gtk.c:235
#53 0x08091ae9 in main (argc=0, argv=0x0) at xchat.c:1006
#54 0x40521767 in __libc_start_main () from /lib/libc.so.6

(gdb) p xtext->draw_buf
$1 = (GdkDrawable *) 0x0


-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------

Offline

#18 2003-10-05 13:18:58

yowwww
Member
Registered: 2003-09-04
Posts: 112

Re: xchat segfaults

he wasn't the only one, my segfaulted too  :evil:

I just deleted my xchat2 hidden file in /home/user/ and then upgraded it again and it was fine. Of course, I lost all my settings, but at least it works.

Offline

#19 2003-10-05 17:59:21

sarah31
Member
From: Middle of Canada
Registered: 2002-08-20
Posts: 2,975
Website

Re: xchat segfaults

perhaps you have not upgraded to the most recent perl?

the previous xchat was looking for perl necessities from 5.8.0 and arch now uses 5.8.1.


AKA uknowme

I am not your friend

Offline

#20 2003-10-06 03:48:31

yowwww
Member
Registered: 2003-09-04
Posts: 112

Re: xchat segfaults

It was strange how  the new  xchat worked perfectly fine on one box of mine but not the other and I am the only one using both with nearly the exact same software and packages on both. I checked for perl as you mentioned and the backup box does not have it installed and it is there where the new  xchat worked fine. I didn't check my other box for perl.  If anything, the main box that has more software on it should have been the one where xchat worked after the upgrade, but it was the reverse.
Either way, it doesn't really matter as it is working fine now, but that was rather strange.
I've only had two packages not work after upgrading so far with pacman (xmms which was fixed by adding alsa-lib) and xchat which was also fixable (even if in an unconventional manner). Overall, the repos seem quite good imho.

Offline

Board footer

Powered by FluxBB