From: Jeff King <peff@peff.net>
To: madmarcos <fru574@my.utsa.edu>
Cc: git@vger.kernel.org
Subject: Re: Java Inflater problem decompressing packfile
Date: Sat, 16 Apr 2011 02:37:29 -0400 [thread overview]
Message-ID: <20110416063729.GC28853@sigill.intra.peff.net> (raw)
In-Reply-To: <1302919505984-6278154.post@n2.nabble.com>
On Fri, Apr 15, 2011 at 07:05:05PM -0700, madmarcos wrote:
> So, my inflater method decompresses the first 7 objects fine (a commit, a
> couple of trees, and several blobs) and a cursory visual inspection of the
> decompressed data seems fine. The eighth object becomes a problem, though.
> It is a blob with the name build.xml that is 51,060 bytes decompressed
> (looking at the original pre-git-pushed jEdit source). The actual file size
> matches the decompressed data content size in the packfile object header.
> The inflater procedure outputs the decompressed data to System.out for
> visual inspection. Approximately the first 1/3 looks like the original
> build.xml but after that, the output is garbled. The procedure continues
> decompressing objects after the 8th, but garbled, object but it dies on the
> 9th object with an "unknown compression method" error.
Is it possible that the blob is stored as a delta within the pack? In
that case the pack header will tell you what the eventual size of the
blob will be, but the data will actually be a diff against another pack
object. Does your inflater handle delta-fied objects?
-Peff
next prev parent reply other threads:[~2011-04-16 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 2:05 Java Inflater problem decompressing packfile madmarcos
2011-04-16 6:37 ` Jeff King [this message]
2011-04-16 14:23 ` madmarcos
2011-04-16 14:36 ` madmarcos
2011-04-16 14:58 ` madmarcos
2011-04-16 15:50 ` madmarcos
2011-04-17 0:40 ` madmarcos
2011-04-17 4:02 ` madmarcos
2011-04-17 4:06 ` madmarcos
2011-04-17 4:36 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110416063729.GC28853@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=fru574@my.utsa.edu \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).