After unpacking your RAR file to get protobuff.log, I examined that file. I believe that file is not a single message, but a set of messages, and each message has a big-endian uint32 stuck in front of it which is the length of the following message. For example, the first four bytes are 0x00, 0x00, 0x00, 0xD4. Deleting those four bytes and then truncating the file to 0xD4=212 bytes resulted in a successful message decode. I didn’t bother trying to do the same with the second or subsequent message, but think it will work.
Chris On Tue, 26 Feb 2013 10:43:20 -0800 (PST) Kheiri Selmi <selmikhe...@gmail.com> wrote: > Hi, > > I am trying to decode the attached file with no success using this > command : protoc --decode_raw < protobuff.log > > I didn't create this file. So I am a bit confused. > > I am thinking the issue can be : > - protobuf version > - file encoding (issue with the the encoding program) > - file have already been zipped with TrueZip java framework > > Thank you > Selmi > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
