>>> On 2014/02/04 at 12:04 PM, Ankit Vani <a...@nevitus.org> wrote: > On Tue, Feb 4, 2014 at 3:27 PM, Bastien Nocera <had...@hadess.net> wrote: >> Try getting a backtrace of the crash. It's likely a bug in the library >> itself. > > Can you tell me how exactly to go about getting a backtrace? > > I've tried using gdb on python (to run g-ir-scanner) without any special > setting, but I'm unable to break on g_log.
Setup PATH, LD_LIBRARY_PATH, etc. needed as per you environment. Do the following: # cd /home/ankit/devel/pidgin-dev/finch/libgnt/ # export GI_SCANNER_DEBUG="save-temps" # make Note the lines (will have different temporary directory prefix) like: ----- (process:13172): GLib-CRITICAL **: g_key_file_has_group: assertion 'key_file != NULL' failed Command '['/home/ankit/devel/pidgin-dev/finch/libgnt/tmp-introspectZP9FjN/Gnt-2.8', '--introspect-dump=/home/ankit/devel/pidgin-dev/finch/libgnt/tmp-introspectZP9FjN/functions.txt,/home/ankit/devel/pidgin-dev/finch/libgnt/tmp-introspectZP9FjN/dump.xml']' returned non-zero exit status -11 ----- then run (as mentioned, "ZP9FjN" will differ): # gdb tmp-introspectZP9FjN/Gnt-2.8 (gdb) r --introspect-dump=tmp-introspectZP9FjN/functions.txt,tmp-introspectZP9FjN/dump.xml You might have to use: # gdb tmp-introspectZP9FjN/.libs/Gnt-2.8 if libtool's wrappers are enabled. Set breakpoints and debug as needed. Hope this helps. Regards, Martin Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list