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
base-64, so that I can see what the bytes are?
On 11 March 2010 14:24, Michael Poole <mdpo...@troilus.org> wrote:
> Roey writes:
> > The problem is, I get a memory access violation when I try to
> > deserialize it :(
> > Unhandled exception at 0x02f166d8 in wmplayer.exe: 0xC0000005: Access
> > violation writing location 0x00000000.
> > Are any of the things I'm doing here wrong , for what I'm trying to do
> > (serialize in C# .NET and deserialize in C++?)
> Most likely yes, but it's hard to suggest what that is without a brief
> code example that shows the crash. The crash is obviously trying to
> write into a null pointer, but only you can find out what code is at
> address 0x02f166d8.
> Michael Poole
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@googlegroups.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at