A vector<int> instance, serialised in C++, is not deserialised correctly in C# about msgpack-cli HOT 7 CLOSED

Thank you for your feedback.

I don't know C++ implementation very well, and there are some possibilities to fail deserialization.
Would you upload serialized binary ("test.test") file?
Or, would you tell me the result of following?

FileStream fs = new FileStream("E:\\test.test", FileMode.Open, FileAccess.Read);
byte[] buf = new byte[fs.Length];
fs.Read(buf, 0, buf.Length);
Console.WriteLine(BitConverter.ToString(buf));

from msgpack-cli.

Hello yfakariya,

Here is the content of test.test extracted exactly as you specified above:

91-9A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A-0D-0A

(Windows confirms the file is 22 bytes in length)

from msgpack-cli.

Thank you sebjf.

I wonder why C++ serializer puts 0x0D in the stream. It looks like just tiny integer value 13, not any header value.
I think the serialized value should be:
91-9A-0A-0A-0A-0A-0A-0A-0A-0A-0A-0A
(12bytes)

MessagePack CLI's unpacker interprets the C++ generated binary as following:

1 element array
  10 elements array, its values are 13, 10...
Extra 10 bytes(13,10,...)

I believe 0x0D after 0x9A represents integer value 13, so I will ask C++ implementers to why msgpack-c outs such values.
Would you tell me what version msgpack-C do you use?

from msgpack-cli.

I use 0.5.4, the same one as available here: http://sourceforge.net/projects/msgpack/files/msgpack/cpp/

Thank you for MessagePack - I was very impressed when looking through the CLI source investigating this bug, this project is quite a feat!

from msgpack-cli.

@sebjf

   myFile.open("E:\\test.test");

This opens a file with text mode. Then 0x0a (LF) is converted to 0x0d 0x0a (CR LF).

You can correct your code:

   myFile.open("E:\\test.test", std::ios_base::binary);

from msgpack-cli.

Ah. Yes. Thank you iwadon! And sorry about the erronous issue.

from msgpack-cli.

@iwadon Thank you for your great post!

from msgpack-cli.