On Mon, Feb 16, 2009 at 03:23:40PM +0100, Alfred M. Szmidt wrote:
> ams@trillian:~/# git --version
> git version 1.6.2.rc1
> ams@trillian:~/# git svn clone REPO -T trunk -b branches -t tags
> [...]
> fatal: Out of memory? mmap failed: Cannot allocate memory
> hash-object -w --stdin-paths: command returned error: 128
>
> Nope, behaves the same way.
Hmm. It would help to know what object it is failing on. I assume you
repo is too large to be easily shared? If not, can you try instrumenting
hash-object with the patch below and seeing which file it is barfing on?
I'd be curious to see the size of the file (in case it is >2G and we
have another signed integer problem) and its position in the list (in
case we are leaking memory and you are hitting a system limit).
---
diff --git a/hash-object.c b/hash-object.c
index 37e6677..20371d0 100644
--- a/hash-object.c
+++ b/hash-object.c
@@ -44,6 +44,7 @@ static void hash_stdin_paths(const char *type, int write_objects)
die("line is badly quoted");
strbuf_swap(&buf, &nbuf);
}
+ fprintf(stderr, "debug: hashing %s\n", buf.buf);
hash_object(buf.buf, type, write_objects, buf.buf);
}
strbuf_release(&buf);
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
