Eric Hanchrow wrote:
> I'm using svn+ssh at work (with 1.4.3 on both client and server), and most
> operations (ci, co, up) succeed, but "log" always fails with "connection closed
> unexpectedly". What could be the cause? How can I debug it?
I've noticed this problem between minor versions when extending the svn
protocol. For me, it's occurred when the client sends a malformed
tuple. There are a couple of abort() calls in the tuple parsing code,
and triggering either of them will result in the server process dieing
and the connection closing unexpectedly.
The easiest way to debug has been to run svnserve under the debugger
with the --listen-once option. I can then catch the abort and figure
out why the serve is dying. Using Wireshark to see the tcp traffic can
also help to determine which request resulted in the abort().
> Oh, and some more data to make it more puzzling:
>
>
> * "svn log" in a different wc -- which is pointing to a different
> machine, also via svn+ssh -- works fine. So it's not the case that
> (for example) "svn log" over svn+ssh is totally broken.
>
>
> * "svn log svn+ssh://localhost/path/to/repos" on the server machine --
> looking at itself, as it were -- works fine.
Received on Thu Jun 14 23:22:39 2007