It will be rather difficult to correct for the error. The point at which the
parse fails may not be the point of corruption: e.g., the corruption may be
in a byte that is part of a varint, and the continuation bit may be set when
it shouldn't. Similarly you could have a corruption in the length
On Jan 20, 2011, at 2:48 , julius-schorzman wrote:
My question is -- can anything be done to retrieve part of the file?
It would be nice to know at which point in the file the problematic
message occurred, and then I could crop to that point or do some
manual exception -- but unfortunately this
Thanks for the tip on CodedInputStream Evan! I will explore it and
if I get anything out of it will report back my findings for anyone
else dealing with this issue.
On Thu, Jan 20, 2011 at 6:27 PM, Evan Jones ev...@mit.edu wrote:
On Jan 20, 2011, at 2:48 , julius-schorzman wrote:
My question
