The invalid memory usage occurs inside the Perl interpreter, not SyncEvolution. You can invoke the "synccompare" script directly to reproduce the problem. It takes two parameters, the old and new database dump.
Those exist in your session directories, see "syncevolution --print-sessions funambol" For example: $ syncevolution --print-sessions -q scheduleworld /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-01-09-47 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-01-09-48 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-01-10-33 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-02-08-50 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-04-17-51 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-22-16-16 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-24-12-34 /home/pohly/.evolution/syncevolution/scheduleworld-2010-02-24-12-35 /home/pohly/.evolution/syncevolution/scheduleworld-2010-03-24-21-31 /home/pohly/.evolution/syncevolution/scheduleworld-2010-03-27-22-01 $ synccompare /home/pohly/.evolution/syncevolution/scheduleworld-2010-03-27-22-01/calendar.before /home/pohly/.evolution/syncevolution/scheduleworld-2010-03-27-22-01/calendar.after David, is there a way for me to get CCed on Debian bug reports for SyncEvolution? -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
