Re: [Evolution] Evolution 1.4 spits multiple 'camel-WARNING...' messages.

[Not Zed <notzed ximian com>]

We tried to remove most of the spurious warnings, but I guess at least
one went through ...

This particular warning means we called a method saying we didn't care
it if failed, and internally its checking for failure ...

So I wouldn't worry about it specifically.  If you would like to help
clear it out to ease your state of mind, you could try generating a
backtrace to pinpoint where it happens, try the following:

gdb evolution
(gdb) r
... do some stuff, until it starts to happen ...
ctrl-c
(gdb) b g_log
(gdb) c
... next time a warning happens, it will stop ...
(gdb) where
... if that doesn't show any call to camel_exception_get_id ... then try
(gdb) theread apply all bt
... if that doesn't show anything, its probably stopped in the wrong
place or something ... *shrug*

And send it to a bug on bugzilla.

These sorts of bugs are trivial to fix.


On Tue, 2003-06-24 at 05:51, Panos Platon Tsapralis wrote:
> While running Evolution (v.1.4) on the command line of an x-terminal, I
> noticed that it repeatedly gives the following message:
>
> (evolution:1397): camel-WARNING **: camel_exception_get_id called with
> NULL parameter.
>
> Evolution runs fine on my system (RH8, fully updated from RHN/Red
> Carpet) - even better than older versions did (e.g., no more crashes
> while managing the "Contacts" folder).
>
> However, I fear that this message may be an indication of a headache
> later on, so, if anybody has a clue on where this message comes from and
> how I can eliminate it, be my guest...
>
> TIA,