Hmm - the data field should be pretty trivial - in terms of the wire-format
it is just a field-header, a length-prefix, and then the raw data.
How big is the message when serialized? (or: how big is a short message that
reproduces this problem?) Could you possibly both the BLOB, either in hex or
b
Roey writes:
[snip]
> The problem is, I get a memory access violation when I try to
> deserialize it :(
> Unhandled exception at 0x02f166d8 in wmplayer.exe: 0xC005: Access
> violation writing location 0x.
>
> Are any of the things I'm doing here wrong , for what I'm trying to do
> (ser
On Mar 11, 2010, at 8:39 , Roey wrote:
Unhandled exception at 0x02f166d8 in wmplayer.exe: 0xC005:
Access violation writing location 0x.
I believe this means you are accessing a NULL pointer somewhere. You
should attach a debugger to your process and look at the stack trace
to
