On Di, 2010-11-23 at 08:27 +0000, [email protected] wrote: > Hi! > > On Mon, 22 Nov 2010, Patrick Ohly wrote: > >> Ok. TLocalEngineDS defines an isDatastoreAlias function, maybe this could > >> be used. There is also a definition for isDatastore, which considers the > >> aliases, but TSyncSession::findLocalDataStore calls > >> TSyncDataStore::isDatastore, although these are TLocalEngineDS objects: > >> > >> typedef std::list<TLocalEngineDS*> TLocalDataStorePContainer; // contains > >> local data stores > > > > Why? I've looked at TLocalEngineDS::isDataStore(), and it does > > everything we need, in particular it checks for the alias: > > Yes, I've seen this, but in my case TSyncDataStore::isDatastore() was > called (according to gdb). There is no code for the aliases. That was the > point, when I got worried. > > Is there something I should try next?
Let's compare notes... is sysync::TLocalEngineDS::isDatastore called? Is it the same call stack as in my email? Where is TSyncDataStore::isDatastore called? Stack backtrace? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
