This problem has reared it's ugly head again. This time, some enums were changed and it caused a crash in an unrelated message when serialized. Padding the message with a bool type at the end of the message fixed it.
It is scary that touching an unrelated part of the .proto file can cause a seg fault (memory free) in the protobuf code when you touch something totally unrelated. On Thursday, April 28, 2016 at 5:58:42 PM UTC-4, Brian Savage wrote: > > I'm using an ARM Cortex A9 running Ubuntu Linux. My application uses > protobufs. I have successfully implemented much of my interface, but there > are a couple of messages that have an integer that is getting padded. For > example, if send decimal 50 (0x32), when it's parsed from the > protomessage, I get 0x32 0x00. The raw data on the send and receive sides > match up (ethernet). Any ideas? > -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
