Hello,
I'm having a strange problem when setting an string value in a protocol
buffer. Keep in mind that my experience in C++ and PB is rather limited.
The .proto file looks more or less like this:
--
package buffers;
message AttributeValue {
enum Type {
INT64
I have exteded data in my .proto file:
option java_outer_classname = Foobar;
message Foo {
optional int32 i = 1;
extensions 10 to 9;
}
message Bar {
extend Foo {
optional int32 j = 10001;
optional string name = 10002;
}
}
message Msg {
optional Foo foo = 1;
The problem is that if I use main-1 the string value is lost when leaving
the scope of the attribute_value() function.
Am I doing something wrong?
On Monday, August 19, 2013 7:17:56 PM UTC+2, Ilia Mirkin wrote:
Perhaps I'm dense, but what's the problem? That gdb doesn't print the
exact
Hi all,
I am having two versions of protobuff ( 2.4.1 and 2.5.0) i want to remove
one off them.
Can any one help me with that?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To unsubscribe from this group and stop receiving emails from it,
Something like protoc --decode_raw?
As for manipulating these in code, there's nothing too great available
if you don't have a descriptor at all. You could create a dummy
message (no fields) and then get them via unknown fields in the
message's reflection object, but they're not easy to
On Mon, Aug 19, 2013 at 8:37 PM, Tom Ward tw...@thefoundry.co.uk wrote:
Basically I'm trying to work out how to deserialize a protobuf message
without using the generated headers, as we're likely to get messages that
weren't generated at compile time. I've looked through the documentation,
I am using protobuf for communication between clients and servers. When I
use valgrind to check the client binary, the following messages are listed.
It seems there is some possible lost memory in
__static_initialization_and_destruction_0. But why does this appear? How
to suppress it?