I agree, the documentation is completely misleading. I just spent an hour
updating to version 2.6.1, assuming maps didn't work because I had version
2.6.0.
I suppose I should have checked here first. It would be nice if the docs
where up to date.
On Monday, July 6, 2015 at 1:39:37 PM UTC-5,
I doubt that anybody will know the answer / solution to this, but since I'm
more or less at my wits end, I figured I'd try.
One a very small number of hosts we're getting this error when an
application which uses the Google Protocol Buffers 2.6.1:
iptor data to disk from one of the affected machines and then
> examining it after the fact to see if it's truncated or somehow otherwise
> corrupted.
>
> On Wed, Oct 5, 2016 at 7:06 AM, Ingmar Koecher <ingmar@gmail.com
> > wrote:
>
>> Sorry, I forgot to
e
> descriptor data to disk from one of the affected machines and then
> examining it after the fact to see if it's truncated or somehow otherwise
> corrupted.
>
> On Wed, Oct 5, 2016 at 7:06 AM, Ingmar Koecher <ingmar@gmail.com
> > wrote:
>
>> Sorry, I forgo
bly every time the application
> starts up?
>
> On Mon, Oct 3, 2016 at 10:54 AM, Ingmar Koecher <ingmar@gmail.com
> > wrote:
>
>> I can now also confirm that this problem only occurs on Windows Server
>> 2003 x86 hosts.
>>
>>
>> On Monda
We've been using protocol buffers for a couple of months (version 2,
exclusively on Windows) and while it works on 99.9% of systems, on a few
systems an application won't start with the following errors:
[libprotobuf ERROR google\protobuf\descriptor_database.cc:315]
Invalid file descriptor data
I can now also confirm that this problem only occurs on Windows Server 2003
x86 hosts.
On Monday, October 3, 2016 at 8:48:48 AM UTC-5, Ingmar Koecher wrote:
>
> We've been using protocol buffers for a couple of months (version 2,
> exclusively on Windows) and while it works on 99.9% o
