Re: Multisync: patch and question

On Fri, 2005-03-11 at 17:57 -0300, Gonzalo Diethelm wrote:
> > What you definitely should do is set the last parameter to a GError * so
> > you can see what evo2 is complaining about :)
> 
> I did that, and got:
> 
> CALENDAR error was Unknown error
> 
> Unluckily, not very useful...
> 
> > I dont think thats the cause. Its the same here.
> 
> Ok, it was a wild guess anyway. Will try with 0.9.

I have another question related to this: how do you effectively debug
Mulsitync 0.8? I tried strace-ing the process (and all the forked
processes as well), hoping to find an open call that would open the
calendar.ics-msyncidX.db file, but could not find it in the traces at
all. I guess this is because Multisync is using some kind of
out-of-process invocation (CORBA?) to query Evolution's DB. If this is
the case, how can I trace the opening, reading and closing of the DB?

If this is all completely off mark, how should I go about finding out
exactly what happens that makes Multisync abort with the "Unknown error"
message?

Regards,


-- 
Gonzalo Diethelm
[email protected]



-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click