Using libpurple in QuteCom (but with assertion fails)

James Wald james.wald at
Wed Sep 3 11:05:55 EDT 2008

2008/9/3 Ethan Blanton <elb at>:
> James Wald spake unto us the following wisdom:
>>Try running Pidgin with
>> G_DEBUG=fatal_criticals in gdb.  This will allow you to get a
>> backtrace at the assert() failure:
>> G_DEBUG=fatal_criticals gdb pidgin
> This is useful only if the assertion is the actual problem.

An assertion failure is an actual problem.  Getting the backtrace
helps us to determine what execution path lead to an assertion
failure.  An assert itself should never be a problem unless it is

Thanks for the clarification of PurplePresence.


More information about the Devel mailing list