Ah, thank you very much Evan. It turned out to be an uninitialized boolean. Properly setting the value in question seems to allow things to proceed normally.
Thanks again, Robby On Mon, Feb 6, 2012 at 11:09 AM, Evan Jones <ev...@csail.mit.edu> wrote: > This is weird. I don't see any clear potential cause, so I have a few > questions: > > > HTMud::EnvAdd item; > > item.set_id(ID); > > item.set_idtype(typeID); > > item.set_x(X); > > item.set_y(Y); > > item.set_z(Z); > > item.set_lockdown(lockdown); > > item.set_mapid(map); > > item.set_tilesetno(tilesetNo); > > item.set_tilesetx(tilesetX); > > item.set_regionx(regionX); > > item.set_regiony(regionZ); > > > Are all these values primitives? Are any of them protocol buffers? > > Have you tried dumping the values that are being set when it dies, and > trying a standalone program that sets the values and calls > SerializeToString to see if it has the same problem? > > Have you made any changes to the protocol buffers library? I'm assuming > you are using the released version of 2.4.1? > > Have you tried running this under valgrind? I'm wondering if there could > be other weird memory corruption that is happening? That seems to be a > frequent cause of "this shouldn't be happening" type errors, particularly > things that appear/disappear occur with optimization enabled/disabled. > > Evan > > -- > http://evanjones.ca/ > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
