From: Masao M. <mu...@hi...> - 2004-02-26 15:28:59
|
Hi, On Wed, 25 Feb 2004 18:06:27 -0800 (PST) Joao Pedrosa <joa...@ya...> wrote: > > Hey :) > > Sometimes my ruby code triggers some assertions on the > C code of the Ruby-GTK+2 bindings, but the returning > error message isn't very helpful for me to fix my > code. For example: > > dewd@heavenknows:~/projetos/irconnector$ ruby > tableview.rb > > (tableview.rb:7717): Gtk-CRITICAL **: file > gtktreestore.c: line 519 > (gtk_tree_store_get_column_type): assertion `index < > GTK_TREE_STORE (tree_model)->n_columns && index >= 0' > failed > > (tableview.rb:7717): GLib-GObject-WARNING **: > gtype.c:2963: type id `0' is invalid > > (tableview.rb:7717): GLib-GObject-WARNING **: can't > peek value table for type `<invalid>' which is not > currently referenced > > [snip] > > Is 7717 from "(tableview.rb:7717)" the supposed line > from the file tableview.rb that's buggy ? Because > tableview.rb has only 314 lines. The message is printed by GTK+ not Ruby/GTK. > I really wanted it to be more accurate on reporting > the buggy line, for obvious reasons. But I don't know > if it's possible. Sure. But now, I don't have good idea. > What's the better way to track such a bug ? Use debug.rb, maybe. -- .:% Masao Mutoh<mu...@hi...> |