Hi,<p>Thank you very much for all comments.<p>I am very suprised for the feedback. I need to clarify my intentions for this project.<p>This tool is a side effect of my main project. I am working on hacking embedded device. During my work, I found out, that device is using Google Protocol Buffers to communicate with Android app and windows C&#x2F;C++ application.
It was my first time with protocol buffers. 
I was looking for any tool, which would help me analyze protobuf messages.
It seems there is none, so I had to learn it by myself :P.<p>&quot;Protocol buffers are Google&#x27;s language-neutral, platform-neutral, extensible mechanism for serializing structured data – think XML, but smaller, faster, and simpler.&quot;<p>How it works:
1. Developer wants to exchange data between different applications&#x2F;systems.
2. One describes data in human readable form in proto file:
      message Person {
         required string name = 1;
         required int32 id = 2;
         optional string email = 3;
      }
3. This file can now be compiled by protoc.
4. Generated code (Java, C++, Python) is then imported to an application.
5. Develoepr can use this code to decode serialized stream.<p>Now - the most important thing. Protoc output code contains serialized descritor of proto file. This descriptor (in serialized way) is included in every application using protobuffs.<p>Once extracted (strings, debugger, any other tool), one can run pbd to disassemble it.<p>In short: Pbd allows to go from point 4. to point 2.
Once descriptors are disassembled, one can rerun pbd to generate code and deserialize protobuffs messages.<p>Hope it clarifies it a bit.<p>This project is in beta. Further work depends on interest and needs. I am very happy to hear more comments and ideas. Thank you for your interest.<p>PS. Pbd name was chosen with premeditaion. It is a bit confusing, but hey - hackers need to be focused :P.<p>BR
Rsc