libprotobuf generally does not rely on dynamic initialization, and instead
uses pthread_once to initialize globals. The stack trace in that bug report
points at an object which is allocated by a pthread_once, so I don't think
initialization ordering can be the culprit here.
On Wed, Jun 24, 2009 at
Protobuf-c has a small bit in its test-suite that uses protobuf's c++
binding to generate packed versions of several messages that are
compared with c binding packed data.
I'm almost tempted to get rid of these fragile tests b/c they are such
a build annoyance. But I'm going to try to keep them
