Bug#339841: Additional Information for Bug#339841

[A. Karl Kornel]

	Hello.  I have some additional information to add to this bug.

	First, I tried to check out a new working copy into a different  
directory (the repository and working copy are still on the same  
system here).  Making the changes to the newly-checked-out copy can  
not be committed (the crash still takes place, and a cleanup/recover  
still needs to be done).

	In addition to the local working copy, I also have access to two  
working copies on remote systems.  Both remote working copies use svn 
+ssh to connect to the repository.  One remote system has version  
1.2.1 (r15230), and another has version 1.1.4 (r13838).  For each  
remote working copy, I updated it to the latest revision (with no  
problems), made a change, and tried to commit.  Each one failed in  
the same place with the following:

> svn: Commit failed (details follow):
> svn: Malformed network data

	Each one required a cleanup/recover.

	In the end I dumped the entire repository, created a repository on a  
different machine, restored the repository onto the "different  
machine", switched the URLs of all checked out working copies, and  
the problem was gone.  The "different machine" is running Darwin  
8.3.0 running Subversion 1.1.4 (r13838).