It sounds like a memory ownership issue. Basically the message object owns
the fields (including the unknown fields). From the stack trace, the string
is probably freed before the destructor is called. Could you please write a
simple function that could reproduce this issue?
On Sun, Feb 26, 2012
hi,
we use proto buff for our c-s application. We find there seem to be no
problems if server proto's optional, repeated field do not exist in
client's proto, so our server and client use different proto defines,
and it works well.
But recently there happens some crash in client proto buff code
