#154 seg fault with xfree 4.2.99.902

closed-works-for-me
nobody
None
5
2003-04-07
2003-02-27
Anonymous
No

I've been able to reproduce this 3 times, so I'm pretty
sure its something with the newer xfree and xchat 2.0.0

With XFree 4.2.99.902 and X-Chat 2.0.0 I've noticed
that after right click ing on a name and that menu
closes, it seg faults. I tried to run it through gdb,
but when it seg'd it froze all of X :/

any more info needed feel free to contact me at
rememberthis(AT)hotmail.com

Discussion

  • Logged In: NO

    Same with XFree 4.3.0 btw

     
  • Peter Zelezny.
    Peter Zelezny.
    2003-03-03

    Logged In: YES
    user_id=5012

    A GDB backtrace would help, overwise I'll close this bug.

     
  • Logged In: NO

    I've noticed X-Chat 2.0.0 and now 2.0.1 segfaults in XFree86
    4.3 also. I get it after it's been running for about a
    minute or two. I thought it was due to a network I was
    trying to connect to being down but when I turned off
    autoconnect for that network and all other networks I saw
    the same problem. I clicked nothing and did nothing in
    X-Chat and it simply segfauled after about a minute and
    half, give or take 30 seconds...

     
  • JP Powers
    JP Powers
    2003-03-08

    Logged In: YES
    user_id=481418

    I've noticed when I run xchat in gdb it seems to simply NOT
    crash. or atleast won't crash in the tim that it crashes
    when I don't run it. It would only seem to me that because
    in gdb DNS becomes faulty there may or may not be a problem
    with that... I'm currently running an xchat in gdb and once
    it crashes, atleast IF it crashes, I'll be sure to post the
    gdb output.

     
  • JP Powers
    JP Powers
    2003-03-08

    Logged In: YES
    user_id=481418

    (gdb) bt
    #0 0x40b33eb5 in Perl_newSVpv () from
    /usr/local/lib/xchat/plugins/perl.so
    Error accessing memory address 0x40b33e6c: No such process.
    (gdb)

    I'm really not terribly sure what that means. I might try
    removing all my scripts and leaving it running again...

     
  • Logged In: NO

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 16384 (LWP 3879)]
    0x403b3359 in g_type_check_instance_is_a () from
    /usr/lib/libgobject-2.0.so.0
    (gdb) bt
    #0 0x403b3359 in g_type_check_instance_is_a () from
    /usr/lib/libgobject-2.0.so.0
    #1 0x401d9cd3 in gtk_widget_event () from
    /usr/lib/libgtk-x11-2.0.so.0
    #2 0x400f39d4 in gtk_main_do_event () from
    /usr/lib/libgtk-x11-2.0.so.0
    #3 0x402b3263 in gdk_event_dispatch () from
    /usr/lib/libgdk-x11-2.0.so.0
    #4 0x404e6155 in g_main_dispatch () from
    /usr/lib/libglib-2.0.so.0
    #5 0x404e459c in g_main_context_dispatch () from
    /usr/lib/libglib-2.0.so.0
    #6 0x404e65dd in g_main_context_iterate () from
    /usr/lib/libglib-2.0.so.0
    #7 0x404e4b5f in g_main_loop_run () from
    /usr/lib/libglib-2.0.so.0
    #8 0x400f31cf in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
    #9 0x0805836b in gtk_widget_grab_focus ()
    #10 0x08095547 in xchat_plugingui_remove ()
    #11 0x40541e34 in __libc_start_main () from /lib/libc.so.6

     
  • Peter Zelezny.
    Peter Zelezny.
    2003-04-07

    • status: open --> closed-works-for-me