-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boost conflict on the noetic branch leads to segfaults #280
Comments
Just to extend, the dependency conflict can be also seen here
|
After some more digging, realized that the C++ support is based on the legacy driver that went EOL some years ago. Are there any plans to support the current C++ driver? (it's boost-free so it would solve the problem), but the new driver has a completely different API: https://stackoverflow.com/questions/45319979/upgrading-mongodb-c-driver-to-mongocxx-3-1-2 |
Hi @jagomo, thanks for finding and investigating this issue. Unfortunately there aren't any plans to support the new C++ driver at this time. The switch would also complicate dependency handling, since it seems the new C++ driver is not on That being said, if you find a solution for this issue, any PRs will be greatly appreciated. |
I've been toying a bit with the new noetic branch trying to update some old code base. In the same node where I make use of MessageStoreProxy I need to make use of boost::thread.
I was getting a segfault randomly happening in the spawned thread. After debugging for a while without a clue. Found out that the resulting node is linking to boost 1.71 (noetic dependency) and 1.67 (libmongoclient dependency). This is known to lead to segfaults in some cases.
https://answers.ros.org/question/190902/two-versions-of-libboost/
Even on the provided message_store_cpp_test this happens:
Is there any way to prevent this and force the usage of one boost library only?
Using Ubuntu 20.04
The text was updated successfully, but these errors were encountered: