On 01/25/2010 10:12 AM, Stefan Sperling wrote: > You could rebuild svn with the --enable-maintainer-mode configure flag. > Then you'll see the file and line number where the error is thrown. > You could then have the client break at the spot in gdb, and post a > backtrace in case it contains anything interesting (like funky-looking > function arguments). This may tell us e.g. if the problem is within > neon or within svn.
I'll see where I get with this. > In addition to the complete neon debug output, a tcpdump -s99999 -X > of the running update would also be nice, to see what client and > server are sending to each other over the wire. This won't be too useful for my situation since everything is done over SSL. Thanks for the tips; I'll post back with what I find. -Doug
signature.asc
Description: OpenPGP digital signature
