Ross Burton wrote: > On Tue, 2007-05-29 at 15:31 +0300, Eddy Petrișor wrote: >> Not sure if this is good enough; as you can see, I didn't knew where to put >> the breakpoint (g_assert was not useful): > > The trick to break on glib assertions is to break on g_logv, which is > the lowest message output function.
Oh, ok. This is just before the message display. Breakpoint 2, 0x00002b898a7d25c0 in g_logv () from /usr/lib/libglib-2.0.so.0 (gdb) bt #0 0x00002b898a7d25c0 in g_logv () from /usr/lib/libglib-2.0.so.0 #1 0x00002b898a7d29d3 in g_log () from /usr/lib/libglib-2.0.so.0 #2 0x00002b898a4662ef in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #3 0x00002b898a466bbd in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #4 0x00002b898a466d61 in g_object_new () from /usr/lib/libgobject-2.0.so.0 #5 0x000000000040ecc9 in category_new (editor=0x59abf0) at koto-task-editor.c:491 #6 0x000000000040f87e in koto_task_editor_init (self=0x59abf0) at koto-task-editor.c:734 #7 0x00002b898a4808f0 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #8 0x00002b898a467c9d in g_object_set () from /usr/lib/libgobject-2.0.so.0 #9 0x00002b898a4660ff in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #10 0x00002b898a466b2c in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #11 0x00002b898a466d61 in g_object_new () from /usr/lib/libgobject-2.0.so.0 #12 0x000000000040a477 in koto_task_editor_dialog_init (self=0x5b6150) at koto-task-editor-dialog.c:225 #13 0x00002b898a4808f0 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #14 0x00002b898a467c9d in g_object_set () from /usr/lib/libgobject-2.0.so.0 #15 0x00002b898a4660ff in g_object_newv () from /usr/lib/libgobject-2.0.so.0 #16 0x00002b898a466b2c in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 #17 0x00002b898a466d61 in g_object_new () from /usr/lib/libgobject-2.0.so.0 #18 0x0000000000408b15 in edit_task (task=0x8f0bc0) at main.c:195 #19 0x00000000004091a9 in on_row_activated (tree_view=<value optimized out>, path=0x9f8580, column=<value optimized out>, user_data=<value optimized out>) at main.c:229 #20 0x00002b898a461479 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #21 0x00002b898a470ae1 in g_signal_chain_from_overridden () from /usr/lib/libgobject-2.0.so.0 #22 0x00002b898a471d95 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #23 0x00002b898a471f73 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #24 0x00002b8988ea9e9b in _gtk_tree_view_column_autosize () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x00002b8988de364d in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #26 0x00002b898a461479 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #27 0x00002b898a470c7f in g_signal_chain_from_overridden () from /usr/lib/libgobject-2.0.so.0 #28 0x00002b898a471b5e in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #29 0x00002b898a471f73 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #30 0x00002b8988eb9e4e in gtk_widget_get_default_style () from /usr/lib/libgtk-x11-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #31 0x00002b8988ddd2ae in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #32 0x00002b8988dde357 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #33 0x00002b898912552c in _gdk_events_init () from /usr/lib/libgdk-x11-2.0.so.0 #34 0x00002b898a7ca913 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #35 0x00002b898a7cd75d in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #36 0x00002b898a7cda46 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #37 0x00002b8988dde6b2 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #38 0x000000000040845a in main (argc=1, argv=0x7fff21f0e5c8) at main.c:570 >> The svn build seems ok. Will you do a 0.8 release; I went back to 0.6 which >> worked fine, but it would be nice to be able >> to set categories right from task creation. > > Cool, I'll make a 0.8 shortly. Excelent. I'll srcinst install it on my etch machine :-) >> BTW, I think that task categorization could be done more intuitive with a >> syntax like "::category:: task". This would >> allow later multiple categorization (e.g.: "::dev::pkg:: release tasks 0.8" >> ;-) ). > > I prefer @foo because it is the same as the Getting Things Done syntax. > Multiple categories will be implemented by splitting the string on ",", > so you'd do @dev,pkg. I was suspecting that GTD was behind the design :-). -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein
signature.asc
Description: OpenPGP digital signature