Re: [SyncEvolution] automated testing of ActiveSync
On Fri, 2011-07-08 at 18:09 +0200, Patrick Ohly wrote:
I am seeing some issues with sync key handling. In some cases, the
activesyncd debug output shows random characters. That looks very much
like an invalid memory access.
I've been running in valgrind (with GSLICE=always-malloc of course), and
apart from false positives on prefetching glibc string functions, it's
generally quiet. So it may give a very quick 'smoking gun' if you
trigger this issue under valgrind, without much noise to churn through.
Is suspect that part of the problem is that
Client::eas_event::Source
needs to "simulate" access by two different clients. Both use the
ActiveSync account defined by
~/.config/syncevolution/client-test/peers/target-config/config.ini
so essentially this looks to the Exchange server like one client.
Is it absolutely necessary that the account ID is a valid email address?
No. Using the email address as the account ID is just a convention.
--
dwmw2