Menu ▾ ▴

#145 Search crash

open
Tim-Philipp Muller
crash (26)
2
2004-01-25
2004-01-06
Anonymous
No

I'm using ed2k-gtk-gui version 0.6.1 on a Debian box.

Client and GUI are running on the same machine.

How to crash it :

Make a search,
Wait for the first answers,
Close the search tab,

Then, the GUI crashes.

Discussion

  • Tim-Philipp Muller

    Tim-Philipp Muller - 2004-01-06
    • assigned_to: nobody --> uberdork
     

  • Tim-Philipp Muller

    Tim-Philipp Muller - 2004-01-06

    Logged In: YES
    user_id=583691

    I've tried this repeatedly, closing the search tab like a
    madman, but I just can't reproduce this :-)

    If you can reproduce this, could you do the following:

    % gdb ed2k_gui
    bla bla bla
    (gdb) run
    ... search and produce the crash ...
    received signal SIGSEGV in bla
    (gdb) bt
    ... send the output here ...
    (gdb) kill
    Do you really want to kill ... ? y
    (gdb) quit
    %

    Cheers
    -Tim

     

  • Nobody/Anonymous

    Nobody/Anonymous - 2004-01-11

    Logged In: NO

    Hi,

    I could reproduced it in the 1st try :o))

    Here is the gdb backtrace :

    (ed2k_gui:28367): Gtk-CRITICAL **: file gtkliststore.c: line
    1884 (gtk_list_store_set_sort_column_id): assertion `header !
    = NULL' failed
    (no debugging symbols found)...(no debugging symbols
    found)...
    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 1024 (LWP 28367)]
    ---Type <return> to continue, or q <return> to quit---
    0x40168125 in gtk_tree_view_get_type () from /usr/lib/libgtk-
    x11-2.0.so.0
    (gdb) bt
    #0 0x40168125 in gtk_tree_view_get_type ()
    from /usr/lib/libgtk-x11-2.0.so.0
    #1 0x401684c4 in gtk_tree_view_get_type ()
    from /usr/lib/libgtk-x11-2.0.so.0
    #2 0x4038c186 in g_timeout_add () from /usr/lib/libglib-
    2.0.so.0
    #3 0x40389a79 in g_get_current_time () from /usr/lib/libglib-
    2.0.so.0
    #4 0x4038a897 in g_main_context_dispatch ()
    from /usr/lib/libglib-2.0.so.0
    #5 0x4038ac73 in g_main_context_dispatch ()
    from /usr/lib/libglib-2.0.so.0
    #6 0x4038b34f in g_main_loop_run () from /usr/lib/libglib-
    2.0.so.0
    #7 0x400ca78f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
    #8 0x08068e63 in gtk_widget_grab_focus ()
    #9 0x403e614f in __libc_start_main () from /lib/libc.so.6

    I hope this could help you.

    ++,

    Vincent

     

  • Tim-Philipp Muller

    Tim-Philipp Muller - 2004-01-11

    Logged In: YES
    user_id=583691

    urgh.

    Unfortunately I have no idea what is happening there.

    Do you always get that Gtk-Critical warning before it crashes?

    If yes, could you do the following:

    % gdb ed2k_gui
    bla..
    (gdb) run --g-fatal-warnings
    ... make crash ...
    Gtk-Critical: bla
    Aborting....
    Received signal SIGABRT in foo
    (gdb) bt
    ... send output of this again ...
    (gdb) kill
    (gdb) quit
    %

    Cheers
    -Tim

    PS: Which Gtk+2.x version are you using?

     

  • Vincent Rossignol

    Vincent Rossignol - 2004-01-12

    Logged In: YES
    user_id=178782

    I could reproduce it one more time :o))

    Here is the new complete backtrace.
    The 1st warning seems to be always there and appears
    before the connection with the core (surely during the
    reading of the configuration file or during the initialization of
    the gui)

    I don't see it usally because I have no console (running
    ed2k_gui from my Linux Box and under exceed - X session for
    Window$).

    My GTK lib version is : 2.0.2-5

    ++,

    Vincent

    PS : forgive my poor english.

    - - - - - - -

    GNU gdb 2002-04-01-cvs
    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 "i386-linux"...(no debugging
    symbols found)...
    (gdb) run --g-fatal-warnings
    Starting program: /usr/bin/ed2k_gui --g-fatal-warnings
    (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)...[New Thread 1024 (LWP
    29630)]
    (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)...

    Gtk-CRITICAL **: file gtkliststore.c: line 1884
    (gtk_list_store_set_sort_column_
    id): assertion `header != NULL' failed
    aborting...
    (no debugging symbols found)...
    Program received signal SIGTRAP, Trace/breakpoint trap.
    [Switching to Thread 1024 (LWP 29630)]
    ---Type <return> to continue, or q <return> to quit---
    0x40390a41 in g_logv () from /usr/lib/libglib-2.0.so.0
    (gdb) cont
    Continuing.
    (no debugging symbols found)...
    Program received signal SIGSEGV, Segmentation fault.
    0x4016814f in gtk_tree_view_get_type () from /usr/lib/libgtk-
    x11-2.0.so.0
    (gdb) bt
    #0 0x4016814f in gtk_tree_view_get_type ()
    from /usr/lib/libgtk-x11-2.0.so.0
    #1 0x401684c4 in gtk_tree_view_get_type ()
    from /usr/lib/libgtk-x11-2.0.so.0
    #2 0x4038c186 in g_timeout_add () from /usr/lib/libglib-
    2.0.so.0
    #3 0x40389a79 in g_get_current_time () from /usr/lib/libglib-
    2.0.so.0
    #4 0x4038a897 in g_main_context_dispatch ()
    from /usr/lib/libglib-2.0.so.0
    #5 0x4038ac73 in g_main_context_dispatch ()
    from /usr/lib/libglib-2.0.so.0
    #6 0x4038b34f in g_main_loop_run () from /usr/lib/libglib-
    2.0.so.0
    #7 0x400ca78f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
    #8 0x08068e63 in gtk_widget_grab_focus ()
    #9 0x403e614f in __libc_start_main () from /lib/libc.so.6
    (gdb) kill
    Kill the program being debugged? (y or n) y
    (gdb) quit

     

  • Tim-Philipp Muller

    Tim-Philipp Muller - 2004-01-12

    Logged In: YES
    user_id=583691

    I think this is probably due to some problem with the (quite
    old) version of gtk+-2.x you are using (current is Gtk+-2.2.4,
    and Gtk+-2.4.0 is coming out in a couple of weeks or so).

    Is that debian stable? I saw that assertion warning once
    myself when running the GUI on debian stable.

    I am not sure though if this is worth debugging unless
    someone can reproduce this problem with Gtk+-2.2.x.

    If you manage to produce the problem again, please try
    exactly what you did last time (run --g-fatal-warnings), but
    then type 'bt' where you typed 'cont' last time (so I know what
    causes that header assertion warning).

    Cheers
    -TIm

     

  • Vincent Rossignol

    Vincent Rossignol - 2004-01-12

    Logged In: YES
    user_id=178782

    Ok,

    This debian is stable, and I had no problem with gtk before
    this one.

    Anyway this bug is not critical... I won't close the tab before
    the search is completed.

    Here is my backtrace for the 1st warning.

    Gtk-CRITICAL **: file gtkliststore.c: line 1884
    (gtk_list_store_set_sort_column_id): assertion `header !=
    NULL' failed
    aborting...
    (no debugging symbols found)...(no debugging symbols
    found)...(no debugging symbols found)...(no debugging
    symbols found)...(no debugging symbols found)...
    Program received signal SIGTRAP, Trace/breakpoint trap.
    [Switching to Thread 1024 (LWP 30235)]
    0x40390a41 in g_logv () from /usr/lib/libglib-2.0.so.0
    (gdb) bt
    #0 0x40390a41 in g_logv () from /usr/lib/libglib-2.0.so.0
    #1 0x40390af9 in g_log () from /usr/lib/libglib-2.0.so.0
    #2 0x400c9848 in gtk_list_store_clear () from /usr/lib/libgtk-
    x11-2.0.so.0
    #3 0x4015dffc in gtk_tree_sortable_set_sort_column_id ()
    from /usr/lib/libgtk-x11-2.0.so.0
    #4 0x0808de88 in gtk_widget_grab_focus ()
    #5 0x0808e5fd in gtk_widget_grab_focus ()
    #6 0x0806e638 in gtk_widget_grab_focus ()
    #7 0x0806968f in gtk_widget_grab_focus ()
    #8 0x08068e54 in gtk_widget_grab_focus ()
    #9 0x403e614f in __libc_start_main () from /lib/libc.so.6

    Thx, ++,

    Vincent

     

  • Tim-Philipp Muller

    Tim-Philipp Muller - 2004-01-25
    • priority: 5 --> 2
     

Log in to post a comment.