Thanks :) Dan
On Wed, Feb 4, 2015 at 10:20 PM, Emmanuele Bassi <eba...@gmail.com> wrote: > hi; > > On 4 February 2015 at 03:19, Daniel Kasak <d.j.kasak...@gmail.com> wrote: > > Hi all. > > > > One of the things that became more difficult with the move to > > introspection-based bindings was figuring out what caused some error > > messages. For example: > > > > (main.pl:25925): Gtk-CRITICAL **: gtk_list_store_get_value: assertion > > 'column < priv->n_columns' failed > > *** unhandled exception in callback: > > *** [gperl_sv_from_value] FIXME: unhandled type - 0 ((null) fundamental > > for (null)) > > *** ignoring at /usr/local/lib64/perl5/5.20.1/Gtk3.pm line 318. > > > > Luckily for me, I know precisely what caused this error, because I just > > changed some code in the area. If I'd just triggered a rare bug that I'd > > introduced a while back, I'd be absolutely lost as to *where* in the code > > this was happening. Is there any way of triggering a full stack trace on > > these kinds of errors? > > $ export G_DEBUG=fatal-criticals > $ gdb --args perl your-app.pl > > then, when the critical warning happens, use `bt` to get the backtrace > of the error. > > you can also use a breakpoint on the `g_logv` function. > > ciao, > Emmanuele. > > -- > https://www.bassi.io > [@] ebassi [@gmail.com] >
_______________________________________________ gtk-perl-list mailing list gtk-perl-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-perl-list
