I think there's an off-by-one error in parsing strings in parseMessage. Whenever a string is parsed, the index is shifted by the length of the string, not accounting for the +1 of the null terminator, meaning my message that contained 2 subsequent strings, and then a bunch of floats, got entirely garbled.
This may have been because coincidentally the index aligned to 4 exactly, without the +1. In other cases, the misalignment would probably catch this issue.
I think there's an off-by-one error in parsing strings in parseMessage. Whenever a string is parsed, the index is shifted by the length of the string, not accounting for the +1 of the null terminator, meaning my message that contained 2 subsequent strings, and then a bunch of floats, got entirely garbled.
This may have been because coincidentally the index aligned to 4 exactly, without the +1. In other cases, the misalignment would probably catch this issue.