I'm guessing your cross compiler setup is somehow mucking up endian logic. Do you have a simple reproducible set up. On Apr 28, 2016 2:58 PM, "Brian Savage" <[email protected]> wrote:
> I am using protobufs on an ARM processor running Ubuntu Linux. Everything > seems to be working, except some integers are being padded with an extra > byte in LSW. > > Take for example the raw message 0x10 0x01 0x48 0x32 > > I'm passing an unsigned integer with a value of 50 decimal (0x32). > Printing the raw data on both sides (the other side is RedHat on Intel) > shows that the message matches up. However, when I call the method to get > the data from the proto message, it comes back as 0x32 0x00 (12800 > decimal). > > Anyone have an idea as to what is going on? This happens with multiple > messages. > > Background - I obtained the protobuf source from github and cross > compiled for the ARM. As I said, there doesn't seem to be any problems > other than the integers. If the integer is large enough that it uses all > 32 bits, it works OK.) > > Thanks > > -- > 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 https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
