Comment #12 on issue 370 by scpet...@osrfoundation.org: static
initialization problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
The patch in comment #10 works for us as well. Is there any chance that it
will be merged? I can generate some code to help reproduce the
Comment #11 on issue 370 by ek.k...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
Great! My solution in the original post requires updating protoc compiler
(libprotoc.so*) and re-generating *.pb.cc files in application side and
Comment #10 on issue 370 by richardg...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
I attach a quick fix to test for identical duplicate message definitons.
Build libprotobuf.so with this & link to it with your .so and binaries
Comment #9 on issue 370 by richardg...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
This is an issue even if you are not unloading shared libraries. We see
this assert when dlopen loads a shared library containing a protobuf cla
Comment #8 on issue 370 by ylee...@gmail.com: static initialization problem
with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
using static library will not have this problem.I did.
reconfigure google buffer with :
configrue --disable-shared
before this step ,modify configure
Comment #7 on issue 370 by ssj...@gmail.com: static initialization problem
with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
you can use protobuf dynamic complier to avoid this problem
--
You received this message because you are subscribed to the Google Groups "Protocol
Bu
Comment #6 on issue 370 by ssj...@gmail.com: static initialization problem
with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
The design of the protobuf library is currently such that if you unload a
dynamic
library containing a protobuf class, you *must* simultaneously unlo
Comment #5 on issue 370 by montoya@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
We did not have this problem in Windows 7 with VisualStudio 2010
:(
Anyway, We finally decided to switch to apache thrift.
--
You received thi
Comment #4 on issue 370 by asierg...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
Same problem. The patch did not fix my issue.
I am using protobuf 2.4.1 in Windows 7 and MingW (gcc version 4.4).
--
You received this message bec
Comment #3 on issue 370 by montoya@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
what I did was to set LOG messages at
src/google/protobuf/descriptor_database.cc
and
src/google/protobuf/message.cc
to warnings, returning true in
Comment #2 on issue 370 by montoya@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
I just tried this fix but it is not working. I will be trying to understand
why.
--
You received this message because you are subscribed to th
Comment #1 on issue 370 by w...@phrenotherapy.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
Has anyone else tried this fix? Do we know if this patch (or the error
that lead to it) have been fixed in 2.4.3?
--
You received this messa
12 matches
Mail list logo
