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
Hi
I have set up gobject-introspection in Pidgin -- and it works well for
libpurple, pidgin and finch. However, g-ir-scanner dies with a very cryptic
error when g-ir-scanner scans libgnt.
The error looks like:
GISCAN Gnt-2.8.gir
(process:13172): GLib-CRITICAL **: g_key_file_has_group:
On Tue, 2014-02-04 at 15:20 +0530, Ankit Vani wrote:
Hi
I have set up gobject-introspection in Pidgin -- and it works well for
libpurple, pidgin and finch. However, g-ir-scanner dies with a very
cryptic error when g-ir-scanner scans libgnt.
The error looks like:
GISCAN Gnt-2.8.gir
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,
On Tue, 2014-02-04 at 15:34 +0530, Ankit Vani 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
