September 2014 - Boost-users - lists.preview.boost.org

from: giridhar
by giridhar 20 Sep '14

20 Sep '14

Salutations boost http://ariasking.com/morning.php/ttqhx3144vcfnpry/ giridhar

1 0

[ASIO] [SSL] [SOCKS4] Layers
by Maciej Miszczak 19 Sep '14

19 Sep '14

Hello, I have been successfully using ASIO for a long time, but recently I try to use SSL over SOCKS 4 and I'm struggling with short read while asynchronous SSL handshaking. I have come across this: http://stackoverflow.com/questions/9943541/boost-asio-how-to-read-write-on-…] but it's only partially helpful. I haven't find any good explanation, what the layers really are (ex. I can't assign next_layer and lowest_layer to any of OSI layers). Could someone explain the meaning of next_layer and lowest_layer and how to use SSL stream with SOCKS 4 proxy. Best regards, Maciej Miszczak

2 2

Re: [Boost-users] Boost XML Serialization
by Manasi Deshpande 19 Sep '14

19 Sep '14

Hello All, Currently I am working on DB Driven C++ API, where it also involves XML processing functionalities. That's where I came across Boost Serialization. We have a very peculiar story here, and it goes like this: We have 2 identical APIs. One in C# and another in C++. Both are DB driven similar APIs. There are instances, where any XML data serialized on C++ platform needs to be de serialized on C# and vice versa. In C# life is straight forward; one needs no bothering about serialization and de serialization. I think in boost you can de serialize the XML document only if it is built using Boost Serialization. I think it is the case in C# also. Is there any way out, where Boost Serialization can be customized? Please forgive me if I am not clear in stating my problem statement! -------------------------------------------------------------------------------------------------- This email and any attachments are confidential and are for the use of the addressee only. If you are not the addressee, you must not use or disclose the contents to any other person. Please immediately notify the sender and delete the email. Statements and opinions expressed here may not represent those of the company. Email correspondence is monitored by the company. This information may be subject to export control regulation. You are obliged to comply with such regulations. Renishaw plc (company number 1106260) and Wotton Travel Limited (company number 01973158) are companies registered in England and Wales with a registered office at New Mills, Wotton-under-Edge, Gloucestershire, GL12 8JR, United Kingdom, Telephone +44 1453 524524. --------------------------------------------------------------------------------------------------

2 1

[logging+unittest]
by Witold E Wolski 19 Sep '14

19 Sep '14

Hi, I need to integrate some loggin into my unit to some extend bein integration tests (hardware). How best to call this function which sets up boost logging void init() { boost::log::add_file_log("sample.log"); boost::log::core::get()->set_filter ( boost::log::trivial::severity >= boost::log::trivial::info ); } if I have a test Runner looking like: #define BOOST_TEST_MODULE MasterTestSuite #include <boost/test/unit_test.hpp> Is there a way not have to add the suites manually Thanks. -- Witold Eryk Wolski

1 1

[thread] memory synchronization multiple mutexes
by firespot 19 Sep '14

19 Sep '14

Hi, How does memory synchronization and visibility behave when multiple mutexes are involved? I have two groups of threads (boost::thread_group) and two mutexes (boost::mutex m1, boost::mutex m2) + associated condition variables, with each thread group being responsible to write to some variables (here Ptr, run) and consistently using "its" mutex for locking. However there is a piece of code that looks - much simplified - like this: void f() { { boost::unique_lock<boost::mutex> Lock(m1); Ptr = someAddress; // set the Ptr from 0 to some memory address } { boost::unique_lock<boost::mutex> Lock(m2); run = 1; // was 0, inform that execution can proceed condVar2.notify_all(); } ... // wait until Ptr has been reset to 0 { boost::unique_lock<boost::mutex> Lock(m1); while (Ptr != 0) condVar1.wait(Lock); } } and another function: void g() { { boost::unique_lock<boost::mutex> Lock(m2); while (run == 0) condVar2.wait(Lock); } // run the execution, e.g. std::copy(Ptr, Ptr + 100, Target); // finally all finished, signal back that Ptr is not needed any more { boost::unique_lock<boost::mutex> Lock(m1); Ptr = 0; condVar1.notify_all(); } } f() is only invoked from a thread of the first group, and g() only from a thread of the second group. Whenever Ptr might get changes the first mutex (m1) and its associated condition-variable is used, and whenver run might get changed the second mutex and its associated conditional variable is used. The control flow guarantees that run is not set to 1 prior to Ptr being set, and thus in g() the "running" itself (here the std::copy) cannot commence earlier. However, what puzzles me now: I used a different mutex for setting Ptr and setting/checking run. Does this have any impact whatsoever on memory visibility across the threads in the two thread-groups? Specifically, is it always guaranteed that when g() continues its execution (because run == 1) that it must see the correct value of Ptr (a non-NULL value)? Or is it possible that it still sees 0 and I'd have to make a separate locking involving m1 to guarantee a proper read for Ptr as anything written under a lock of m1 is also only guaranteed to be later properly read if the locking also used m1? thanks!

2 1

[mpl] simple mpl::transform with placeholder?
by Andrew King 19 Sep '14

19 Sep '14

Hi, Lets say I have an mpl vector defined as : template <typename Traits> struct A { }; template <typename Traits> struct B { }; typedef mpl::vector<A<mpl::_>, B<mpl::_> > MyVec; struct MyTraits {}; How do I 'apply' or transform MyVec with MyTraits? ie. I want the mpl::vector ... boost::mpl::vector<A<MyTraits>, B<MyTraits>>; I realise I can do mpl::apply<A<mpl::_>, MyTraits> to get A<MyTraits> but I can't work out how to do the equivalent to the entire vector. mpl::transform seems like what I should be using. Transform seems to do apply internally, but I can't work out the syntax to do something like: using substituted = typename boost::mpl::transform<MyVec, boost::mpl::apply<boost::mpl<_>, MyTraits> >::type; (This isn't right!) It may be I am confused because inside the transform, boost::mpl::_1 is the item in the vector, not the 'inner' placeholder. Sorry if this is a basic question ... Regards, Andrew

1 0

[Thread] Read-write locks
by lfrfly＠icqmail.com 18 Sep '14

18 Sep '14

I'm trying to create a standard read/write lock using Boost Threads, and I'm having a bit of difficulty mapping the Boost concepts onto the usual ones. A read/write lock should have several states: Locked for reading (multiple threads may lock at once), locked for writing (only one thread may lock, and no threads may be locked for reading at the same time), and unlocked. Ideally it would be nice if an RWL which is locked for reading may temporarily upgrade to locked for writing, then return to the locked for reading state. Boost supports several relevant notions of locking: shared locking, upgrade locking, and exclusive locking. This to me is a confusing distinction. In particular, a shared_mutex seems appropriate as the basis for a RWL, but is lock_upgrade() the equivalent of a write lock and lock_shared the equivalent of a read lock? This is unclear. If "upgrade locking" is not the same as "exclusive locking", then is an upgrade lock actually exclusive? Could someone please clarify this.

4 3

Numeric Cast from integer to floating point
by dariomt＠gmail.com 17 Sep '14

17 Sep '14

Hi, Quoting the docs for boost::numeric_cast: "There are several situations where conversions are unsafe: [...] Conversions from floating point types to integral types." What about conversions from integral types to floating point types? E.g. from 64bit int to double. The following example shows what I mean: #include <iostream> #include <cmath> #include <boost/numeric/conversion/cast.hpp> int main() { const uint64_t i = 123445678911188878; std::cout << "i=" << i << std::endl; const double d = i; std::cout << "d=" << std::fixed << d << std::endl; std::cout << "next=" << std::fixed << std::nextafter(d, std::numeric_limits<double>::max() ) << std::endl; std::cout << "prev=" << std::fixed << std::nextafter(d, -std::numeric_limits<double>::max()) << std::endl; // I'd expect the following cast to fail const double dd = boost::numeric_cast<double>(i); std::cout <<"dd=" << std::fixed << dd << std::endl; return 0; } prints i=123445678911188878 d=123445678911188880.000000 next=123445678911188896.000000 prev=123445678911188864.000000 dd=123445678911188880.000000 because that integer cannot be represented in double precision Is there something in Boost to help here? Thanks in advance

5 4

value_type in Typed In Place Factory
by Adam Badura 17 Sep '14

17 Sep '14

According to header file boost/utility/typed_in_place_factory.hpp (as linked from documentation: http://www.boost.org/doc/libs/1_55_0/boost/utility/typed_in_place_factory.h…) typed_in_place_factory has member type value_type which is the constructed type. Yet documentation ( http://www.boost.org/doc/libs/1_55_0/libs/utility/in_place_factories.html) fails to mention it. Why? Is it not part of the interface (I would assume so based on not mentioning it in documentation...)? Or was it just forgotten? I find such value_type quite useful... And since I'm already writing let me note that the mentioned documentation has also another minor issue. In Specification section the sample in_place_factory and typed_in_place_factory should be named in_place_factory1 and typed_in_place_factory1. As this is how they are really named. Or it should be stated explicitly that the actual name is implementation dependent. Adam Badura

1 0

Boostlog and ASIO crash in shared library
by Ray Cheng 17 Sep '14

17 Sep '14

Hi, My project use a simple main using dlopen to "run" the real main function in target shared library. I use both Boost Log and ASIO (for threadpool) in the project. In Linux I found the ASIO got weird behavior with some un-initialized variables and crashing all the time. I am able to trim down my problem into a small program as below: // *** threadpool.cpp *** #include <iostream> #include <memory> #include <boost/asio/io_service.hpp> #include <boost/bind.hpp> #include <boost/thread/thread.hpp> void print() { std::cout << "print" << std::endl; } struct ThreadPool { void start() { boost::asio::io_service ioService; boost::thread_group threadpool; std::unique_ptr<boost::asio::io_service::work> work = std::make_unique<boost::asio::io_service::work>(ioService); threadpool.create_thread(boost::bind(&boost::asio::io_service::run, &ioService)); for (int i=0; i<100; ++i) { ioService.post(&print); } std::cout << "Post all calculation tasks" << std::endl; work.reset(); threadpool.join_all(); ioService.stop(); std::cout << "Finished all calculation tasks" << std::endl; } }; extern "C" void createthreadpool() { ThreadPool pool; pool.start(); } // *** threadpool.cpp *** g++ -O0 -std=gnu++1y -fPIC -c -g -DLinux -DGNU_GCC -I${BOOST_HOME}/include threadpool.cpp g++ -shared -o libthreadpool.so threadpool.o -L${BOOST_HOME}/lib -lboost_system -lboost_date_time -lboost_thread -lboost_filesystem -lboost_regex -lboost_chrono -ldl -lstdc++ // *** main.cpp *** #include <dlfcn.h> #include <iostream> int main(int argc, char** argv) { typedef void* createProcess(); auto service = dlopen("libthreadpool.so", RTLD_LAZY); createProcess* make = reinterpret_cast<createProcess*>(dlsym(service, "createthreadpool")); std::cout << "dlsym" << std::endl; make(); return 0; } // *** main.cpp *** g++ -O0 -std=gnu++1y -fPIC -c -g -DLinux -DGNU_GCC main.cpp // Link against boost_log to simulate my problem (although it is not using any boost_log). This version will crash g++ -o main.bad main.o -L${BOOST_HOME}/lib -lboost_system -lboost_date_time -lboost_thread -lboost_filesystem -lboost_regex -lboost_chrono -lboost_log -ldl -lstdc++ // it works fine If link against libthreadpool, surprising me g++ -o main main.o -L/home/sysmmbuild/dev/boost -lthreadpool -L${BOOST_HOME}/lib -lboost_system -lboost_date_time -lboost_thread -lboost_filesystem -lboost_regex -lboost_chrono -lboost_log -ldl -lstdc++ One more finding is, if compile boost_log without thread support, the main.bad also working fine. I have attached the code and make.sh as make script. Software version Redhat enterprise 6.5 g++ 4.9.1 Boost 1.56.0 Rgds, Ray

2 2