locnv | 27 May 12:11 2015

Error on building project in release mode using Visual studio 2013

I had a project which is using protobuf C-Sharp ( unity3d engine )

And then I build project into Windows phone project and I got this

 - The project build and run perfectly on "Debug mode" and "Master mode"
 - But come into the "Release mode" I got this exception ( and it also crash my application at the start of the app )

A first chance exception of type 'System.TypeLoadException' occurred in WinRTBridge.ni.DLL
A first chance exception of type 'System.TypeInitializationException' occurred in WinRTBridge.ni.DLL
A first chance exception of type 'System.TypeInitializationException' occurred in WinRTBridge.ni.DLL
A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.ni.dll
A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in Microsoft.Phone.ni.dll
A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in Microsoft.Phone.ni.dll
A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.ni.dll
A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in System.Windows.ni.dll

When I remove the proto file , I got the project build normally on both Debug , Master and Release mode

So can someone help me to look at this ?

The version of Proto C-Sharp is the newest I get from nuget ( v 2.4.1.555 )

Thanks.


--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Attachment (gsystem.cs): text/x-csharp, 556 KiB
Julian Della Bosca | 27 May 02:15 2015
Picon

Implementing protocol buffers in a Maven project using NetBeans

Hi all,

I am in the process of creating a file feed with Java in a NetBeans Maven project and want to use protocol buffers. Can any one point me in the direction of a good tutorial or good documentation I should start with? Any thing specific to NetBeans would be very helpful. 

I have tried to turn the protocol buffers source code into a jar file with NetBeans but I get numerous error's about not being about not being able to find symbols and package FieldDescriptorProto not existing. I would very much appreciate any help with this. 

Regards
Julian Della Bosca

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Tom Fan | 27 May 06:29 2015
Picon

How to optimize the dynamic message parse/serialization speed

I found that the parse/serialization speed of the dynamic message is much slower than the static generated message.
How to optimize the dynamic message parse/serialization speed

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Mason Cubes | 21 May 12:59 2015
Picon

protobuf encoded message

I am trying to understand a protobuf encoded message. the message is given below, it is apparently a 64 byte long hash value, but I cannot understand the encoding process

    12 01 40 30 37 62 65 37 36 30 34 32 33 35 32 37
    33 30 64 64 63 37 38 35 39 39 38 39 34 66 31 31
    37 65 30 37 34 35 36 61 37 64 30 37 66 62 36 31
    64 39 38 32 31 62 32 36 61 38 33 34 61 34 30 66
    64 62 38


The first byte says the following is a byte or string wire type and the second byte says only one byte in the byte or string array. Then the third byte 0x40 it must be the length of the field i.e 64. If I consider this byte as a varint tag content then the rest of the contents does not make sense, unless it is a repeated field with integers only 1 byte values all the way to the end.

I cannot understand how it was decoded. I don't have the proto file used to encode the message.  

Can someone give me a hint?

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
navin kurle | 21 May 11:59 2015
Picon

how can i delete file using proto buffer

Hey guys,

i want to delete a file from diferent ip (machine)

can some one help me

thanks in advance

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Tak Wong | 20 May 06:13 2015
Picon

getAllFields performance?

We are using protobuf as our messaging, and each message, we loop thru the set fields, and do something with it.

We loop it using

for ( final Map.Entry<Descriptors.FieldDescriptor, Object> entry : msg.getAllFields().entrySet()) { FieldDescriptor field = entry.getKey(); Object value = entry.getValue();

Under profiler, we found that this GetAllFields uses most of the time, and I did some research, and it looks like there is no other way.

I know that we can use do something like this:

for ( final FieldDescriptor field : msg.getDescriptorForType().getFields()) { if (!msg.hasField(field)){ continue; } Object value = message.getField(field);

But getDescriptorForType returns all the fields rather than just the set ones.

Does anyone know of another better performing way to loop thru the fields? I believe the problem with getAllFields are creating a new map each time, and also reflection. Can i force it to use Trove map inside rather than a regular hashmap?

Thanks.


--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Nils Lukas | 19 May 11:42 2015
Picon

Working with Protocol Buffers on Visual Studio 2003

Dear Community,

I have spent some time trying to run Google Protobuf with Visual Studio 2003, though it was built for Visual Studio 2008. My work requires me to do so, because they have not yet migrated to a newer version of Visual Studio. Unfortunately, my efforts resulted in this error:

C:\CustomMods\include\google\protobuf\stubs\atomicops_internals_x86_msvc.h(46) : fatal error C1189: #error : "We require at least vs2005 for MemoryBarrier"


Is there any hack or workaround to that error?
I would be glad if someone could help me out.

Kind regards,
Nils L.

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
俞勇 | 15 May 04:19 2015
Picon

How to get all messages name in a proto file

Hi, 
    I have doing some coding related to generated c++ code based proto file. now i just use shell grep to find all message name in a proto file
 Is there any protobuf funciton to get all message name?

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Jim Muchow | 19 May 20:35 2015
Picon

Secret Message Pre-Header

I sent a question yesterday, but I don't see it as having been posted, much less 
responded to. My apologies for the redundancy if my original message is in some 
queue somewhere.

**********

I'm trying to determine the utility of Valgrind in an app. The app uses protocol buffers.

I am seeing a message from Valgrind

Syscall param write(buf) points to uninitialised byte(s)

with the following info

Address 0x11c7fa02 is 2 bytes inside a block of size 8,192 alloc'd

At first, I thought it might be one of the fields in a message declared optional, but 
when I filled out the field, I got the same warning. In the process of looking into this 
more closely I was able to dump the buffer:

0x00    0x01    0xc1    0x09    0x00    0x00    0x00    0x10 <---- secret, pre-header?
0x08    0x00    0x10    0xa5    0xcb    0x96    0xad    0x0a
0x1a    0x06    0x61    0x70    0x61    0x63    0x68    0x65

The latter 16 bytes are the message proper with three fields and I understand how 
they are created and interpreted from the Encoding spec (very helpful). It is the first 
eight bytes I don't  understand.

These first bytes are almost like a secret pre-header. It looks to me as if the last four 
bytes are a 32-bit length field. The number matches in this case and in the other case in 
which the optional field was left unset. I can't figure what the first four bytes indicate. In
particular, the bytes 0xc1 and 0x09, which would start the area of the supposedly 
uninitialized bytes.

Is there somewhere in the code I can look to see how this pre-header is created. Or I 
would be happy to research this myself if some documentation exists, but I don't know
where to start looking.

Thanks for any help,
jdm

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Jim Muchow | 18 May 23:11 2015
Picon

Secret Protobuf Pre-header?

I looking at an asserted problem with protobufs. As reported by Valgrind:

Syscall param write(buf) points to uninitialised byte(s)

In trying to track this down, I have come across what looks to me to be
a pre-header that comes before the regular message info. For example:

    0x00    0x01    0xc1    0x09    0x00    0x00    0x00    0x10
    0x08    0x00    0x10    0xa5    0xcb    0x96    0xad    0x0a
    0x1a    0x06    0x61    0x70    0x61    0x63    0x68    0x65

What I am trying to understand is those first 8 bytes. The rest of the
message, the ensuing 16 bytes, I understand.

In trying to decode this pre-header, I've come up with some guesses

0x00    0x01 <------------------------ two fields? one?
0xc1    0x09 <------------------------ proto version?
0x00    0x00    0x00    0x10 <-------- total length of the following? Is always correct

Valgrind seems to think that the uninitialised bytes start at offset 2.

Just looking for info about this data. I've found the Encoding spec
which was helpful in decode the rest of the data, but not this header.

Thanks for any help,
jdm

--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
PEDRO sanchez | 12 May 21:22 2015
Picon

error when running make check in protobuf-2.6.1

I am trying to compile bitcoin but i get an error from google protocol buffers.I managed to install protobuf 2.6.1 yesterday but i keeps sending me the error so i decided to install it again but this time from a diferent folder(last time i did it from Downloads and now from a folder i've created called software),but now when i run the make check :

~/Software/protobuf-2.6.1$ make check
Making check in .
make[1]: Entering directory `/home/pedro/Software/protobuf-2.6.1'
make  check-local
make[2]: Entering directory `/home/pedro/Software/protobuf-2.6.1'
Making lib/libgtest.a lib/libgtest_main.a in gtest
make[3]: Entering directory `/home/pedro/Software/protobuf-2.6.1/gtest'
make[3]: `lib/libgtest.la' is up to date.
make[3]: `lib/libgtest_main.la' is up to date.
make[3]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/gtest'
make[2]: Leaving directory `/home/pedro/Software/protobuf-2.6.1'
make[1]: Leaving directory `/home/pedro/Software/protobuf-2.6.1'
Making check in src
make[1]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
make  check-am
make[2]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
make  protoc protobuf-test protobuf-lazy-descriptor-test protobuf-lite-test test_plugin zcgzip zcgunzip
make[3]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
make[3]: `protoc' is up to date.
make[3]: `protobuf-test' is up to date.
make[3]: `protobuf-lazy-descriptor-test' is up to date.
make[3]: `protobuf-lite-test' is up to date.
make[3]: `test_plugin' is up to date.
make[3]: `zcgzip' is up to date.
make[3]: `zcgunzip' is up to date.
make[3]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make  check-TESTS
make[3]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
/home/pedro/Software/protobuf-2.6.1/src/.libs/lt-protobuf-test: error while loading shared libraries: libgtest.so.0: cannot open shared object file: No such file or directory
FAIL: protobuf-test
/home/pedro/Software/protobuf-2.6.1/src/.libs/lt-protobuf-lazy-descriptor-test: error while loading shared libraries: libgtest.so.0: cannot open shared object file: No such file or directory
FAIL: protobuf-lazy-descriptor-test
PASS
PASS: protobuf-lite-test
Testing output to zip...
Testing output to jar...
./google/protobuf/compiler/zip_output_unittest.sh: 89: jar: not found
Warning:  'jar' command not available.  Skipping test.
PASS
PASS: google/protobuf/compiler/zip_output_unittest.sh
+ TESTFILE=Makefile
+ cmp - Makefile
+ gunzip
+ ./zcgzip
+ gzip
+ cmp - Makefile
+ ./zcgunzip
PASS: google/protobuf/io/gzip_stream_unittest.sh
==========================================
2 of 5 tests failed
Please report to protobuf <at> googlegroups.com
==========================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make: *** [check-recursive] Error 1


the make:




~/Software/protobuf-2.6.1$ make
make  all-recursive
make[1]: Entering directory `/home/pedro/Software/protobuf-2.6.1'
Making all in .
make[2]: Entering directory `/home/pedro/Software/protobuf-2.6.1'
make[2]: Leaving directory `/home/pedro/Software/protobuf-2.6.1'
Making all in src
make[2]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
make  all-am
make[3]: Entering directory `/home/pedro/Software/protobuf-2.6.1/src'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make[2]: Leaving directory `/home/pedro/Software/protobuf-2.6.1/src'
make[1]: Leaving directory `/home/pedro/Software/protobuf-2.6.1'



--
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, send an email to protobuf+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

Gmane