[Unison-hackers] How to chase a xferbycopying bug?

[Benjamin Pierce]

One possibility is that this behavior was introduced by the fix that  
Jerome and I made the other day to address the "Aborted..." problem.   
I still do not entirely understand what is going on there myself (the  
problem was a tricky interaction between transfer threads), but at  
least I can upgrade to 2.19.1 on all my machines and see if I have  
the same issue.

One question: Is the shortcut happening on the client or the server?   
(I.e., which direction is Unison trying to copy the file?)

     - B


On Jan 23, 2006, at 3:44 AM, Alan Schmitt wrote:

> Hello,
>
> I'm using the current svn version of unison (2.19.1), and I might  
> have found a bug: sometimes, when synchronizing, I get a "remote  
> server has unexpectedly quit" (or something like this), that I can  
> easily reproduce (i.e. it's impossible to synchronize, the server  
> always quits). Looking at using.log, I found that this always  
> happened when doing a "Shortcut: copying ...". It does not happen  
> all the time, but setting xferbycopying to false let me complete  
> the synchronization.
>
> I don't really know how to chase this bug (more precisely, how to  
> get debug information from the server). Any suggestion as how to  
> proceed?
>
> Thanks,
>
> Alan
>
> -- 
> Alan Schmitt <http://sardes.inrialpes.fr/~aschmitt/>
>
> The hacker: someone who figured things out and made something cool  
> happen.
> .O.
> ..O
> OOO
>
>
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers