I looking at an asserted problem with protobufs. As reported by Valgrind:
Syscall param write(buf) points to uninitialised byte(s)
In trying to track this down, I have come across what looks to me to be
a pre-header that comes before the regular message info. For example:
0x00 0x01 0xc1 0x09 0x00 0x00 0x00 0x10
0x08 0x00 0x10 0xa5 0xcb 0x96 0xad 0x0a
0x1a 0x06 0x61 0x70 0x61 0x63 0x68 0x65
What I am trying to understand is those first 8 bytes. The rest of the
message, the ensuing 16 bytes, I understand.
In trying to decode this pre-header, I've come up with some guesses
0x00 0x01 <------------------------ two fields? one?
0xc1 0x09 <------------------------ proto version?
0x00 0x00 0x00 0x10 <-------- total length of the following? Is
always correct
Valgrind seems to think that the uninitialised bytes start at offset 2.
Just looking for info about this data. I've found the Encoding spec
which was helpful in decode the rest of the data, but not this header.
Thanks for any help,
jdm
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
