Google Git
Sign in
pigweed / third_party / github / protocolbuffers / protobuf / f4f9aec52f5b4c46ff32fb9527229da081a14e11
commitf4f9aec52f5b4c46ff32fb9527229da081a14e11[log] [tgz]
authorPetr Prokhorenkov <prokhorenkov@gmail.com>Thu Apr 14 11:17:54 2016 +0300
committerPetr Prokhorenkov <prokhorenkov@gmail.com>Thu Apr 21 09:27:33 2016 +0300
tree02d8ff141ad7e0228bfcf6b2f5ee1322c5df5fbd
parent814685ca2cd9280ca401e1842fd6311440921a0a [diff]
Fix bug with silent message corruption in LITE_RUNTIME.

A protobuf message will be corrupted in the following scenario:
  1. Use LITE_RUNTIME.
  2. Have an optional enum field following some other field.
  3. Update protocol by adding new values to the enum.
  4. Have an old client parse and serialize a message having enum field
      set to a value the client does not understand.
  5. Field preceeding the enum is now corrupted.

The bug is due to the fact that optimized fallthrough in parser code
does not update variablle 'tag' when jumping to the parser code for the
next field.
3 files changed
tree: 02d8ff141ad7e0228bfcf6b2f5ee1322c5df5fbd
  1. benchmarks/
  2. cmake/
  3. conformance/
  4. csharp/
  5. editors/
  6. examples/
  7. java/
  8. javanano/
  9. jenkins/
  10. js/
  11. m4/
  12. more_tests/
  13. objectivec/
  14. php/
  15. protoc-artifacts/
  16. python/
  17. ruby/
  18. src/
  19. util/
  20. .gitignore
  21. .travis.yml
  22. appveyor.bat
  23. appveyor.yml
  24. autogen.sh
  25. BUILD
  26. CHANGES.txt
  27. configure.ac
  28. CONTRIBUTORS.txt
  29. generate_descriptor_proto.sh
  30. gmock.BUILD
  31. LICENSE
  32. Makefile.am
  33. post_process_dist.sh
  34. protobuf-lite.pc.in
  35. protobuf.bzl
  36. protobuf.pc.in
  37. Protobuf.podspec
  38. README.md
  39. six.BUILD
  40. tests.sh
  41. update_file_lists.sh
  42. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

Build Status Build status

Copyright 2008 Google Inc.

https://developers.google.com/protocol-buffers/

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can find protobuf's documentation on the Google Developers site.

This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.

Protocol Compiler Installation

The protocol compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.

For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our release page:

https://github.com/google/protobuf/releases

In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.

If you are looking for an old version that is not available in the release page, check out the maven repo here:

http://repo1.maven.org/maven2/com/google/protobuf/protoc/

These pre-built binaries are only provided for released versions. If you want to use the github master version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.

If you would like to build protoc binary from source, see the C++ Installation Instructions.

Protobuf Runtime Installation

Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:

LanguageSource
C++ (include C++ runtime and protoc)src
Javajava
Pythonpython
Objective-Cobjectivec
C#csharp
JavaNanojavanano
JavaScriptjs
Rubyruby
Gogolang/protobuf
PHPTBD

Usage

The complete documentation for Protocol Buffers is available via the web at:

https://developers.google.com/protocol-buffers/