[Bug 110] Changed - Seg Fault lors d'ouverture de cat?gorie

============================================================================
THIS MESSAGE WAS GENERATED BY THE BUGTRACKER SOFTWARE PLEASE DO NOT REPLY

INSTEAD FOLLOW BUG'S URL BELOW IN ORDER TO DETAIL BUG:
============================================================================
         Bug #: 110 (http://www.grisbi.org/bugtracking/bug.php?op=show&bugid=110)
   Reported By: [email protected]
   Modified By: [email protected]
----------------------------------------------------------------------------
       Summary: Seg Fault lors d'ouverture de catégorie
           URL: http://onclebens.free.fr/grisbi_segfault.jpg
       Product: Grisbi stables versions
       Version: 0.4.1
     Component: Grisbi - Main
!       Status: Closed
!   Resolution: Fixed
      Severity: Annoyance
    OS/Version: Debian Linux
      Priority: 1 - Low
   Assigned To: 
============================================================================
                              COMMENTS

----- Posted by Dionysos at 5:18 PM on 11-15-2003 -----
Oouups !!
Me suis trompé de message, désolé, voici le bon.

Salut ,
Voici les réponses de GDB :

Program received signal SIGSEGV,
Segmentation fault.
0x08075d8e in ouverture_node_categ ()
(gdb) bt
#0
 0x08075d8e in ouverture_node_categ ()
#1  0x401d403f in
gtk_marshal_NONE__POINTER () from /usr/lib/libgtk-1.2.so.0
#2
 0x40203b6c in gtk_signal_remove_emission_hook () from
/usr/lib/libgtk-1.2.so.0
#3  0x40202fd5 in gtk_signal_set_funcs () from
/usr/lib/libgtk-1.2.so.0
#4  0x402010b3 in gtk_signal_emit () from
/usr/lib/libgtk-1.2.so.0
#5  0x40199c68 in gtk_ctree_get_type () from
/usr/lib/libgtk-1.2.so.0
#6  0x4019b7a8 in
gtk_ctree_post_recursive_to_depth () from /usr/lib/libgtk-1.2.so.0
#7
 0x4019b77d in gtk_ctree_post_recursive_to_depth () from 
/usr/lib/libgtk-1.2.so.0
#8  0x4019b77d in
gtk_ctree_post_recursive_to_depth () from /usr/lib/libgtk-1.2.so.0
#9
 0x4019c618 in gtk_ctree_expand_to_depth () from
/usr/lib/libgtk-1.2.so.0
#10 0x0806ca51 in demande_expand_arbre ()
#11
0x401d41b5 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0
#12 0x40203b6c in gtk_signal_remove_emission_hook () from
/usr/lib/libgtk-1.2.so.0
#13 0x40202fd5 in gtk_signal_set_funcs () from
/usr/lib/libgtk-1.2.so.0
#14 0x402010b3 in gtk_signal_emit () from
/usr/lib/libgtk-1.2.so.0
#15 0x40172068 in gtk_button_clicked () from
/usr/lib/libgtk-1.2.so.0
#16 0x401735ed in gtk_button_get_relief ()
from /usr/lib/libgtk-1.2.so.0
#17 0x401d41b5 in gtk_marshal_NONE__NONE
() from /usr/lib/libgtk-1.2.so.0
#18 0x40202e6f in gtk_signal_set_funcs
() from /usr/lib/libgtk-1.2.so.0
#19 0x402010b3 in gtk_signal_emit ()
from /usr/lib/libgtk-1.2.so.0
#20 0x40171fa8 in gtk_button_released ()
from /usr/lib/libgtk-1.2.so.0
#21 0x40172f58 in gtk_button_get_relief
() from /usr/lib/libgtk-1.2.so.0
#22 0x401d3e3f in
gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
#23
0x40203013 in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0
#24
0x402010b3 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0
#25
0x40237acb in gtk_widget_event () from /usr/lib/libgtk-1.2.so.0
#26
0x401d3d85 in gtk_propagate_event () from /usr/lib/libgtk-1.2.so.0
#27
0x401d2eee in gtk_main_do_event () from /usr/lib/libgtk-1.2.so.0
#28
0x40281457 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0
#29 0x401324d8 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#30 0x40132ae3 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#31 0x40132c7c in g_main_run () from /usr/lib/libglib-1.2.so.0
#32
0x401d27e7 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#33 0x080981fd
in main ()
#34 0x40a2ada6 in __libc_start_main () from /lib/libc.so.6
(gdb)

J'espÚre que ça suffira à trouver l'erreur.
Salut et
Fraternité,
Ben


----- Posted by benj at 11:29 PM on 11-23-2003 -----
+ J'ai en *théorie* corrigé ce bug, mais je n'arrive pas à le
+ reproduire, donc difficile de se prononcer.

La seule maniÚre dont
+ Grisbi puisse planter à cet endroit là a été corrigée, donc ce problÚme
+ ne devrait plus advenir.  Maintenant ... quelles sont les conditions qui
+ ont créé cette instabilité ?  Le mystÚre reste ouvert.




-- 
Pour vous desabonner envoyez un mail a [email protected]