Sander,
You are right, the original messages came when using the Cygwin shell.
However, I get the same error when using cmd.exe
C:\rhensle\hac74work\outreach_trunk\classes\abaton\demographics>\devtool
s\svn\svn-win32-0.30.0\svn diff -r127:128 Staff.java
Index: Staff.java
===================================================================
--- Staff.java (revision 127)
+++ Staff.java (revision 128)
@@ -36,1724 +36,1731 @@
svn: Not enough storage is available to process this command.
svn: svn_diff_file_output_unified: error writing hunk.
C:\rhensle\hac74work\outreach_trunk\classes\abaton\demographics>
-----Original Message-----
From: Sander Striker [ mailto:striker@apache.org
<mailto:striker@apache.org> ]
Sent: Friday, October 10, 2003 11:13 AM
To: Hensley, Richard
Cc: users@subversion.tigris.org
Subject: RE: Unsure as to what an error message is really telling me
> From: kfogel@newton.ch.collab.net [ mailto:kfogel@newton.ch.collab.net
<mailto:kfogel@newton.ch.collab.net> ]On
> Behalf Of kfogel@collab.net
> "Hensley, Richard" <Richard.Hensley@McKesson.com> writes:
> > I get the following message when I execute a diff command:
> >
> > wc $svn diff -r 127:128 Staff.java
> > Index: Staff.java
> > ===================================================================
> > --- Staff.java (revision 127)
> > +++ Staff.java (revision 128)
> > @@ -36,1724 +36,1731 @@
> > svn: Not enough storage is available to process this command.
> > svn: svn_diff_file_output_unified: error writing hunk
> >
> > I'm not sure what the error messages mean.
>
> Based on the error message, the line numbers in your diff, and the
> existence of this issue (which Sander Striker is hard at work on)
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1481
<http://subversion.tigris.org/issues/show_bug.cgi?id=1481>
>
> I'm tempted to say that svn was unable to diff a very large file
> because it was unable to hold it all in memory :-).
No. This is when the code is already hitting the output stage,
that is, after the diff has been created. The output code is
simply reading in the file again to output the relevant portions.
However, the error is related to writing to stdout, which is
odd.
Seeing the '$' prompt in your report, I assume you are not using
the windows native shell, but something else. Could you try
running the same command from cmd?
Thanks,
Sander
Received on Mon Oct 13 18:09:52 2003