Hi All,
Any suggestions where the messages below come from? I've run outa time and patience.
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed *
They seem to happen when only on the first time I select a tab of filetype None so I'm guessing its something in symbols?
Geany git HEAD, gtk 2.24.10 glib 2.30.2.
Cheers Lex
On 12-07-06 06:25 PM, Lex Trotman wrote:
Hi All,
Any suggestions where the messages below come from? I've run outa time and patience.
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed
They seem to happen when only on the first time I select a tab of filetype None so I'm guessing its something in symbols?
Geany git HEAD, gtk 2.24.10 glib 2.30.2.
Hi,
Compile with `-DG_FATAL_WARNINGS` and then run in gdb. It'll abort and you can see where it happened.
Cheers, Matthew Brush
Le 07/07/2012 19:34, Matthew Brush a écrit :
On 12-07-06 06:25 PM, Lex Trotman wrote:
Hi All,
Any suggestions where the messages below come from? I've run outa time and patience.
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed
(geany:2673): Gtk-CRITICAL **: IA__gtk_tree_store_remove: assertion `VALID_ITER (iter, tree_store)' failed
They seem to happen when only on the first time I select a tab of filetype None so I'm guessing its something in symbols?
Geany git HEAD, gtk 2.24.10 glib 2.30.2.
Hi,
Compile with `-DG_FATAL_WARNINGS` and then run in gdb. It'll abort and you can see where it happened.
…or run in GDB with G_DEBUG=fatal-warnings envvar set.
Sorry not to have replayed to this mail but it was fixed yesterday on IRC, leading to GP commit https://github.com/geany/geany-plugins/commit/b6020c34cb9723a6378a381388f567...
Cheers, Colomban
On 07/07/2012 19:01, Colomban Wendling wrote:
Compile with `-DG_FATAL_WARNINGS` and then run in gdb. It'll abort and
you can see where it happened.
…or run in GDB with G_DEBUG=fatal-warnings envvar set.
Personally I use gdb with: r --g-fatal-warnings bt
Nick