I have figured it out by myself.
The problem is that _DecodeVarint() may only consume fewer than the 4 bytes
reserved for it and reports how long it really was in the second return
tuple element. So progressing offset by that returned value rather than 4
does the trick.
Cheers,
Moose
Mr Moose
Hello everyone,
I hope I can find some advise here.
I have C++ code that writes a number of protobuf messages to a compressed
size delimited stream like this (simplified):
FILE *ofile = fopen("myfile.bin.gz", "wb");
google::protobuf::io::FileOutputStream ostream(_fileno(ofile));
Hi Romain,
On 9 Dez., 12:10, Romain François francoisrom...@free.fr wrote:
http is quite verbose for sending protobuf message around, but it is
likely to be implemented for a lot of languages.
we did just this here. We wrote an RPC implementation complete with
HTTP transport and protobuf as
Jul., 08:33, Mr Moose stephan.men...@gmail.com wrote:
Kenton,
well, I checked this over and over again and I really think I did make
sure. I also checked the linker settings for all other libs I link
against and they are all set to Debug. Also, this is the same build
environment I used
Enjoy!
S.
On 16 Jul., 01:42, Kenton Varda ken...@google.com wrote:
Hi all,
I will be on vacation and not checking e-mail through July 22nd. I've asked
fellow protobuf dev Jason to help answer questions in the meantime, but if
you see a question that isn't answered and you know the answer,
obscure but I
tend to think _SECURE_SCL might alter headers and type definitions to
the using app and the lib are using differently sized types.
Cheers,
Stephan
On 16 Jul., 09:29, Mr Moose stephan.men...@gmail.com wrote:
OK, just for the records: Now I can be really sure. I've deleted
Hi there,
I am experiencing crashes in a protocol buffers file using debug build
on windows (VC2005). On Linux, debug or not and on Windows release
everything is fine but when I try to run the code on debug it raises
an assertion to crash right afterwards. I'm using 2.1
here's what the
