tag:blogger.com,1999:blog-6586841944500000900.post851442175599347039..comments2020-02-20T16:13:47.921-05:00Comments on The Programming Blog of Adam Hodges: Cross-platform communication using Google's Protocol Buffers RevisitedAdamhttp://www.blogger.com/profile/15245889336941344249noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6586841944500000900.post-90933781817935858762013-11-10T16:39:27.044-05:002013-11-10T16:39:27.044-05:00Thank You! You blog post saved at least couple of ...Thank You! You blog post saved at least couple of days ...<br />Unknownhttps://www.blogger.com/profile/08963607425496850490noreply@blogger.comtag:blogger.com,1999:blog-6586841944500000900.post-12588558367449756342013-09-27T13:11:32.642-04:002013-09-27T13:11:32.642-04:00Oh! I'm sorry ...i'm very distracted :-).....Oh! I'm sorry ...i'm very distracted :-)...I'm gonna to check my installation. I'm using version 2.4.1. Thank you very much, i'll let you know :-)Pierohttps://www.blogger.com/profile/12911534597749339176noreply@blogger.comtag:blogger.com,1999:blog-6586841944500000900.post-84728092305954367912013-09-27T12:49:34.515-04:002013-09-27T12:49:34.515-04:00Piero,
I am far from a protobuf expert, but it lo...Piero,<br /><br />I am far from a protobuf expert, but it looks like there's something wrong with your installation. This seems to be the root of the problem: 131 google/protobuf/message_lite.cc: No such file or directory.<br /><br />I'm not sure what else would cause this. Check that you installed protobuf properly. What version of protobuf are you using? I used 2.3 to make this guide, so it's possible there have been changes to the library since then.Adamhttps://www.blogger.com/profile/15245889336941344249noreply@blogger.comtag:blogger.com,1999:blog-6586841944500000900.post-59228418053400650902013-09-27T10:00:18.902-04:002013-09-27T10:00:18.902-04:00Hi Adam,
i followed your code to handle a TCP prot...Hi Adam,<br />i followed your code to handle a TCP protobuf connection between two<br />processes, but i have a crash into the protobuf library when i'm going to parse<br />the sent message. Above you can see some infos about code and traces.<br />Could you help me??? Thank you very much!<br /><br /><br />/**<br /> ** [0] This is the dump of the sent message:<br /> ** - first byte (0x08) should be the varint len, that is the "header"<br /> ** - others bytes should be the payload of the proto message (len = 8 bytes)<br /> **/<br />[line: 180, tag buffer3] 08 08 01 1a<br />[line: 180, tag buffer3] 04 08 0a 10<br />[line: 180, tag buffer3] 14<br /><br />/**<br /> ** [1] This is the dump of the received message after removing the varint len <br /> **/<br />[line: 77, tag ParseMsg(1)] 08 01 1a 04<br />[line: 77, tag ParseMsg(1)] 08 0a 10 14<br /><br />/* [2] Above the code to parse the message */<br />google::protobuf::io::ArrayInputStream arrIn(buffer, len);<br />google::protobuf::io::CodedInputStream input(&arrIn);<br />google::protobuf::io::CodedInputStream::Limit msgLimit = input.PushLimit(len);<br />input.PopLimit(msgLimit);<br /><br />msgp->ParseFromCodedStream(&input);<br /><br />/* [3] Above is showed the crash happened into the ParseFromCodedStream */<br />Program received signal SIGSEGV, Segmentation fault.<br />0x00157ba2 in InlineParseFromCodedStream (this=0xbffff190, input=0xbfffed08) at google/protobuf/message_lite.cc:131<br />131 google/protobuf/message_lite.cc: No such file or directory.<br /> in google/protobuf/message_lite.cc<br />Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6.i686 libgcc-4.4.6-4.el6.i686 libstdc++-4.4.6-4.el6.i686 zlib-1.2.3-27.el6.i686<br />(gdb) bt<br />#0 0x00157ba2 in InlineParseFromCodedStream (this=0xbffff190, input=0xbfffed08) at google/protobuf/message_lite.cc:131<br />#1 google::protobuf::MessageLite::ParseFromCodedStream (this=0xbffff190, input=0xbfffed08) at google/protobuf/message_lite.cc:161<br />#2 0x0804f05f in PceMgr::ParseMsg(unsigned char*, int, pceGenericMessage*) ()<br />#3 0x0804f3f9 in PceMgr::Run() ()<br />#4 0x0808450e in main ()<br />Pierohttps://www.blogger.com/profile/12911534597749339176noreply@blogger.comtag:blogger.com,1999:blog-6586841944500000900.post-49004665890782258182013-08-08T10:38:03.739-04:002013-08-08T10:38:03.739-04:00You're absolutely right... I blame my lack of ...You're absolutely right... I blame my lack of experience with NIO! Thanks for pointing that out.Adamhttps://www.blogger.com/profile/15245889336941344249noreply@blogger.comtag:blogger.com,1999:blog-6586841944500000900.post-55568078328093015762013-08-07T13:52:27.029-04:002013-08-07T13:52:27.029-04:00Your java receiving has the same issue!Your java receiving has the same issue!Anonymoushttps://www.blogger.com/profile/02794976446081905240noreply@blogger.com