- Boost-users - lists.boost.org

1.57.0 link errors (missing ctor/dtor for boost::archive::detail::shared_ptr_helper)
by David Abdurachmanov 13 Nov '14

13 Nov '14

Hi, I am moving to Boost 1.57.0 and having issues with some code related to serialization. https://github.com/cms-sw/cmssw/blob/CMSSW_7_3_X/CondFormats/Serialization/… https://github.com/cms-sw/cmssw/blob/CMSSW_7_3_X/CondFormats/Serialization/… In both cases the problem is here: #if BOOST_VERSION >= 103500 #include <boost/archive/shared_ptr_helper.hpp> #endif [snip] #if BOOST_VERSION >= 103500 // mix-in helper class for serializing shared_ptr , public boost::archive::detail::shared_ptr_helper #endif A similar (or the same) problem is reported here: http://boost.2283326.n4.nabble.com/Serialization-link-error-in-1-56-td46668… It seems that ctor/dtor are not exported anymore: /testSerializationDQMObjects.o: In function `eos::portable_oarchive::portable_oarchive(std::ostream& , unsigned int)': testSerializationDQMObjects.cpp:(.text._ZN3eos17portable_oarchiveC2ERSoj[_ZN3eos17portable_oarchiveC5ERSoj]+0x54): undefined reference to `boost::archive::detail::shared_ptr_helper: :shared_ptr_helper()' testSerializationDQMObjects.cpp:(.text._ZN3eos17portable_oarchiveC2ERSoj[_ZN3eos17portable_oarchiveC5ERSoj]+0x1c1): undefined reference to `boost::archive::detail::shared_ptr_helper ::~shared_ptr_helper()' boost::serialization::shared_ptr_helper does not seem to be a drop-in replacement at first look. There is also 'shared_ptr_helper_base', but is only available in the implementation file. Is such mix-in class still available in a new Boost version? Thanks, david

1 0

[serialization] Treatment of corrupt archives - assert vs. exception throw
by Gabriel Redner 13 Nov '14

13 Nov '14

Hi folks, I'm dealing with binary archives which may have been corrupted enroute to my code. My naive expectation was that the serialization library should throw an exception when it encounters something in the input stream it doesn't understand (in which case my code can react gracefully). But, I've found that: 1. There exist cases where serialization will just assert and bring down the process 2. The documentation suggests that an exception should be thrown, but I didn't find any strong statement of this, so I am not sure whether it is a contract of the library. My first and most pressing question is: is it a guarantee of the library that invalid input should result in an exception and not an assert? If this is not so, I think it should be documented much more clearly. If it is so, then this message is a bug report. There's an assert in archive/basic_binary_iprimitive.hpp:98 that can be triggered if the bytes in the archive which represent a bool actually contain a value other than 0 or 1. One can trigger this in a test case like so (on x86_64 Linux, at least): ========== #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <fstream> int main() { { std::ofstream of("archive.bin", std::ios_base::binary); boost::archive::binary_oarchive oa(of); unsigned char i = 2; oa << i; } { std::ifstream f("archive.bin", std::ios_base::binary); boost::archive::binary_iarchive ia(f); bool b; // note different type than what was saved, but same size ia >> b; // assert! } } ========== Let me know if this is a bug that I should report to the tracker, or a feature. Thanks, -Gabe

3 3

BGL - shortest widest path
by Mark Fanara 13 Nov '14

13 Nov '14

I am trying to find the "shortest-widest path" between a single source and target node in an undirected graph (less than 25 nodes). (In my case, a shortest widest path is the maximum bandwidth path. If there are several such paths, it is the one with the least number of hops.) See W i k i p e d i a entry on "Widest path problem" I have successfully used dijkstra_shortest_paths() with a custom combine() function to find the maximum bandwidth path, however this does not take into account the possibility of more than one path with the same maximum bandwidth. In that case, I am looking for the one with the fewest hops. I am not clear on the meaning of some of the graph theory terms --- Is the problem I am trying to solve similar too, or the same as, a maximum flow problem? If so, as I am using an undirected graph, which boost algorithm should I use and how should I create a directed graph from my undirected graph? Would really appreciate an example, perhaps something that prints the resulting vertices in from-source-to-sink order.

1 0

[Test] failure linking tests dynamically
by Latimerius 12 Nov '14

12 Nov '14

Hello, I'm evaluating Boost.Test. I did the initial evaluation using the header-only variant and now I'd like to move to dynamic linking the Test library for a larger-scale deployment. However, all attempts so far failed due to Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 I'd put it down to my lack of experience with Test, or Boost in general, however I noticed that my libs/test/example's don't seem to build either. I'm on OS X Yosemite. I compile Boost with ./bootstrap.sh --prefix=<my_dir> ./b2 cxxflags="-stdlib=libc++" linkflags="-stdlib=libc++" ./b2 install As this doesn't seem to compile the necessary .dylibs I added <define>BOOST_TEST_DYN_LINK=1 <link>shared to the "requirements" section of the first target in libs/test/build/Jamfile.v2 and rebuilt just Boost.Test. Although I don't actually know what I was doing, this did seem to build the Boost.Test dynamic libraries, which tests are however failing to link against. The result looks the same on 1_56_0 and 1_57_0. Could someone please help me find the problem? I'm dubious about my building procedure in particular, could someone give me a complete sequence of steps necessary to build Boost with Boost.Test ready to be linked dynamically? I check the documentation, which is good and detailed but deals with various aspects in isolation and doesn't give a newcomer a good idea of the overall process. Cheers!

2 4

boost.container.vector::operator==() bug?
by niXman 11 Nov '14

11 Nov '14

Hi, https://github.com/boostorg/container/blob/master/include/boost/container/v… Explained: if ( !(1 != 1) ) Another question is, why 'memcmp()' not used for vectors of fundamental types? -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___________________________________________________ Another online IDE: http://liveworkspace.org/

4 10

lockfree::spsc_queue & move semantics
by Thomas Danckaert 11 Nov '14

11 Nov '14

I'd like to use a spsc_queue of unique_ptr's to bigger objects, to transfer ownership between threads. That way, I can create/allocate an object in a non-realtime thread, then transfer ownership to a realtime thread using a lockfree queue, and, using another queue, pass on the unique_ptr to another thread that takes care of cleanup when the realtime thread no longer needs the it. For example: boost::lockfree::spsc_queue<unique_ptr<string>, boost::lockfree::capacity<10> > cb; Unfortunately, spsc_queue does not use move semantics (methods to push onto the queue take parameters as const reference and construct a copy in the queues internal storage), so i can not cb.push() a unique_ptr<string> onto my queue. Is it reasonable to want to add this, and if so, what would be the best place to submit a request? (I managed to get a simple example working by adding rvalue reference overrides of the queue's push() methods, and using std::move in the pop() method) bool push(T && t) { }; Also, I noticed that the destructor for the spsc_queue (with size fixed at compile-time) does not run destructors for it's contents. What could be the reason for this? Thomas

2 1

[scope_exit] 1.57 MSVC C4003 warning
by Filip Konvička 11 Nov '14

11 Nov '14

Hi, Any use of BOOST_SCOPE_EXIT in 1.57 seems to emit warning C4003 on MSVC 2012 and 2013: warning C4003: not enough actual parameters for macro 'BOOST_PP_EXPAND_I' Uncomment either line to suppress the warning. Is BOOST_PP_VARIADICS enabled by mistake for MSVC (especially 2013)? Should I explicitly set BOOST_PP_VARIADICS=0 for MSVC? Despite the warning, the code appears to work fine (i.e., the block of code gets properly called). Thanks, Filip #include <boost/version.hpp> #if defined(_MSC_VER) && BOOST_VERSION==105700 //#pragma warning(disable:4003) //#define BOOST_PP_VARIADICS 0 #endif #include <boost/scope_exit.hpp> #include <iostream> int main(int argc, char* argv[]) { int x=0; BOOST_SCOPE_EXIT((x)) { std::cout << "here " << x << std::endl; } BOOST_SCOPE_EXIT_END return 0; }

3 5

boost property tree for recursive structures
by Maurizio Vitale 11 Nov '14

11 Nov '14

Hello everybody, I'm trying to use the boost property tree library to represent recursive data structures, but although I can get the dumped json to look reasonable, I cannot traverse the ptree in any ways I've tried. The code below, compiles and run, except for the call to Dump in DumpAssign. Is there a way to traverse arbitrary trees where values can be themselves ptrees? I'm about to throw the towel and go with boost::seriaization, but I did like the traversal mechanisms property trees offer. Any suggestion? Thanks, Maurizio #include <boost/any.hpp> #include <boost/assign/list_of.hpp> #include <boost/foreach.hpp> #include <boost/property_tree/json_parser.hpp> #include <boost/property_tree/ptree.hpp> #include <boost/property_tree/xml_parser.hpp> #include <iostream> #include <string> #include <vector> #include <map> using boost::property_tree::ptree; using boost::assign::list_of; using boost::assign::map_list_of; using namespace std; ptree Op(string type, ptree a1, ptree a2) { ptree pt; // pt.put_value(type); pt.put("type", type); ptree args; args.push_back(make_pair("", a1)); args.push_back(make_pair("", a2)); pt.add_child("args", args); return pt; } ptree Net(string name) { ptree pt; pt.put("type", "net"); pt.put("name", name); return pt; } ptree Assign(ptree lhs, ptree rhs) { ptree pt; pt.put("type", "assign"); pt.add_child("lhs", lhs); pt.add_child("rhs", rhs); return pt; } string Dump(ptree::value_type e); string DumpConcat(ptree::value_type e) { string result = "{"; bool first = true; BOOST_FOREACH(const ptree::value_type& child, e.second.get_child("args")) { if (not first) { result += ", "; first = false; } result += Dump(child); } return result + "}"; } string DumpNet(ptree::value_type e) { return e.second.get<std::string>("name"); } string DumpAssign(ptree::value_type e) { string result = "assign "; // HOW TO HAVE A RECURSIVE CALL TO Dump(lhs) HERE? result += Dump(?); return result; } string DumpNop(ptree::value_type) {return "NOP";} string Dump(ptree::value_type e) { static std::map<string, string(*)(ptree::value_type)> dump = map_list_of ("net", DumpNet) ("concat", DumpConcat) ("assign", DumpAssign) ("nop", DumpNop) ; string type = e.second.get<string>("type", "nop"); return dump[type](e); } int main(int, char**) { ptree pt; ptree a1; a1.push_back(make_pair("", Assign( Op("concat", Op("concat", Net("a1"), Net("a1")), Net("w")), Net("a2")))); pt.add_child("operators", a1); cout << "=============\n"; write_json(std::cout, pt); cout << "=============\n"; BOOST_FOREACH(const ptree::value_type& e, pt.get_child("operators")) { cout << "> " << Dump(e); } }

1 0

Boost.Python shared_ptr bug?
by Christoff Kok 11 Nov '14

11 Nov '14

Hi, I found an issue when accessing a shared_ptr C++ object in Python using Boost.Python. When I try to access an attribute of the shared_ptr object read from an C++ object, I get an error telling me that the attribute does not exist. When I use raw pointers instead of shared_ptr, then there is no issue. Also, when using raw pointers, accessing an item in a list of base class objects returns the object in as the derived most class. This is wanted. When I use shared_ptrs however, the derived most object is of the base class type. This is not wanted. I am sure the Boost.Python developers should be aware of these two issues by now. If so, is there any plans to fix this? If so, when? Below is a test showing this issue: *Raw pointers:* #include<memory> #include<vector> struct Vehicle{ virtual ~Vehicle(){} int testAttribute; }; struct Boat: public Vehicle { virtual ~Boat(){} int testBoatAttribute; }; struct Garage { std::vector<Vehicle*>& vehicleList() { return m_VehicleList; } std::vector<Vehicle*> m_VehicleList; }; #include <boost/python.hpp> #include <boost/python/suite/indexing/vector_indexing_suite.hpp> BOOST_PYTHON_MODULE(garage_ext) { using namespace boost::python; class_<Garage>("Garage") .def("vehicleList", &Garage::vehicleList, return_internal_reference<1>()); class_<Vehicle,Vehicle*,boost::noncopyable>("Vehicle", no_init) .def_readwrite("testAttribute", &Vehicle::testAttribute); class_<Boat,Boat*,bases<Vehicle>>("Boat") .def_readwrite("testBoatAttribute", &Boat::testBoatAttribute); implicitly_convertible<Boat*, Vehicle*>(); class_<std::vector<Vehicle*> >("stl_vector_Vehicle_ptr") .def(vector_indexing_suite<std::vector<Vehicle*>>()); } *Shared pointers:* #include<memory> #include<vector> #include <boost/shared_ptr.hpp> struct Vehicle{ virtual ~Vehicle(){} friend bool operator==(const Vehicle& lhs, const Vehicle& rhs) { return true; } int testAttribute; }; struct Boat: public Vehicle { virtual ~Boat(){} friend bool operator==(const Boat& lhs, const Boat& rhs) { return true; } int testBoatAttribute; }; struct Garage { friend bool operator==(const Garage& lhs, const Garage& rhs) { return true; } std::vector<boost::shared_ptr<Vehicle>>& vehicleList() { return m_VehicleList; } std::vector<boost::shared_ptr<Vehicle>> m_VehicleList; }; #include <boost/python.hpp> #include <boost/python/suite/indexing/vector_indexing_suite.hpp> BOOST_PYTHON_MODULE(garage_ext){ using namespace boost::python; class_<Garage>("Garage") .def("vehicleList", &Garage::vehicleList, return_internal_reference<1>()); class_<Vehicle,boost::shared_ptr<Vehicle>,boost::noncopyable>("Vehicle", no_init) .def_readwrite("testAttribute", &Vehicle::testAttribute); class_<Boat,boost::shared_ptr<Boat>, bases<Vehicle>>("Boat") .def_readwrite("testBoatAttribute", &Boat::testBoatAttribute); implicitly_convertible<boost::shared_ptr<Boat>, boost::shared_ptr<Vehicle>>(); class_<std::vector<boost::shared_ptr<Vehicle>> >("stl_vector_Vehicle_ptr") .def(vector_indexing_suite<std::vector<boost::shared_ptr<Vehicle>>>()); } *Python test:* from garage_ext import * g = Garage() l = g.vehicleList() newboat = Boat() newboat.testAttribute = 3 newboat.testBoatAttribute = 5 l.append(newboat) print(type(l[0])) print(str(hasattr(l[0],"testAttribute"))) print(str(l[0].testAttribute)) b = l[0] print(type(b)) print(str(b.testBoatAttribute)) print("Done.") *Raw pointer result:* <class 'garage_ext.Boat'> True 3 <class 'garage_ext.Boat'> 5 Done. *Shared pointer result:* <class 'garage_ext.*Vehicle*'> *// Expected it to be Boat as with Raw pointers* Traceback (most recent call last): File "test_garage.py", line 9, in <module> print(str(hasattr(l[0],"testAttribute"))) *// Expected attribute to exist as with Raw pointers. Note: dir(l[0]) shows that it has the attribute. Accessing the attribute however throws an error.* Boost.Python.ArgumentError: Python argument types in None.None(Vehicle) did not match C++ signature: None(Vehicle {lvalue}) Kind Regards, Christoff

1 0

MSM library: documentation graphics
by Ricardo Cruz 10 Nov '14

10 Nov '14

Dear all, I am considering adopting boost MSM library for the statecharts in my project. It looks awesome. The documentation has several graphical representations of the state machines: http://www.boost.org/doc/libs/1_57_0/libs/msm/doc/HTML/index.html They look automatically generated. Are they? If so, what tool was used? I did not find that information anywhere in the documentation. Sorry if I miss it. Best wishes, Ricardo Cruz

2 1