On Fri, 2008-05-16 at 18:59 +0530, svalbard colaco wrote:
> Can any on tell me how to debugg the same...Has any one come across
> these warnings...?
> And what colud be the possible approach to handle them....

Run evolution under GDB and set a breakpoint at the function "g_logv".
That will make the program stop every time one of these warnings are
printed.  You can then issue a backtrace command and see where in the
code the warning is coming from.

Matthew Barnes

Evolution-hackers mailing list

Reply via email to