Re: [Evolution] Very serious problem with evo-exchange 2.11.5

["Paul D. Smith" <psmith gnu org>]

> From your description of the bug, Yes, what you seem to be hitting is
> some consequence of syncing some updates.  IIUC, I just leave a system
> running evolution-exchange and fetching mails, should reproduce this
> issue, isn't it, Paul?

Yes, it should.

> Let me prepare a system and watch it for a day to reproduce.  Meanwhile,
> any lead in anyway to narrow it down to any particular scenario will be
> much useful for me to quickly jump into the issue and solve it.

I don't have too much helpful to say about this.  I'm on vacation at
the moment so I don't have access to Evo for debugging, etc.  If you
can't reproduce it I can try to figure out whether it's a particular
message or type of message that causes the problem.  I always am
running the debug versions of Evo under full debugging and keeping the
log files, but there doesn't seem to be any messages.

One thing I've noticed about the Evo code in the past is that it
doesn't do hardly any error checking.  Functions don't check their
arguments for things like NULL pointers very often, and they also
often don't check the return values of other functions to verify that
they're sane.  Because of this, debug output isn't as useful as it
could be and core dumps often happen at a distance (sometimes a far
distance) from where the error actually occurs.  I haven't looked at
the code since the 2.6/2.8 versions so maybe it's gotten better
since.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith gnu org>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist