- Boost-users - lists.boost.org

MPI_ERR_TRUNCATE with Boost.MPI and only blocking communication
by Alex Cumberworth 21 Jun '21

21 Jun '21

I am trying to run some Monte Carlo simulation code I wrote in C++ with MPI via the Boost.MPI wrapper. I use only blocking send and receive calls (i.e. send and recv, never isend or irecv), but after running the program for a few days, I inevitably end up with the following error terminate called after throwing an instance of boost::exception_detail::clone_impl >' what(): MPI_Recv: MPI_ERR_TRUNCATE: message truncated I have seen that this can happen with non-blocking calls are being made, but I cannot see how it can happen with only blocking calls. I am sending and receiving a vector of structs: struct Chain { bool operator==(Chain chain_2); int index; int identity; vector positions; vector orientations; private: friend class boost::serialization::access; template void serialize(Archive& ar, const unsigned int version) { ar& index; ar& identity; ar& positions; ar& orientations; } }; using Chains = vector; where VectorThree is declared elsewhere as class VectorThree { public: VectorThree(int x, int y, int z): m_container {{x, y, z}} {}; VectorThree(): m_container {{0, 0, 0}} {}; VectorThree operator-(); VectorThree operator+(const VectorThree& v_2) const; VectorThree operator-(const VectorThree& v_2) const; bool operator!=(const VectorThree& v_2) const; int& operator[](const size_t& i) { return m_container[i]; }; const int& at(const size_t& i) const { return m_container.at(i); }; VectorThree rotate_half(VectorThree axis); VectorThree rotate(VectorThree origin, VectorThree axis, int turns); VectorThree rotate(VectorThree axis, int turns); int sum(); int abssum(); VectorThree absolute(); VectorThree sort(); private: array m_container; friend class boost::serialization::access; template void serialize(Archive& arch, const unsigned int) { arch& m_container; } }; It sends and receives instances of this object many times before the error occurs. I have narrowed down the calls where the error occurs by printing statements before and after both sending and receiving. The sending code: Chains chains_send {m_us_sim->get_chains()}; cout << "Win " << m_rank << ": Sending chains (size " << chains_send.size() << ") to " << win_i << "\n"; m_world.send(win_i, swap_i, chains_send); cout << "Win " << m_rank << ": Sent chains to " << win_i << "\n"; The receiving code: Chains chains_rec; cout << "Win " << m_rank << ": Recieving chains from " << win_to_win[0] << "\n"; m_world.recv(win_to_win[0], swap_i, chains_rec); cout << "Win " << m_rank << ": Recieved chains (size " << chains_rec.size() << ") from " << win_to_win[0] << "\n"; In the output file before the crash I have Win 0: Recieving chains from 1 Win 1: Sending chains (size 2) to 0 Win 1: Sent chains to 0 I am using version 1.65 of Boost and OpenMPI 2.0.1.

2 1

newbie, Getting Started on Unix Variants
by John 15 Jun '21

15 Jun '21

Please someone help me work through the Getting Started on Unix Variants. I've completed the steps up until 6 Link Your Program to a Boost Library. However, the library shown in the step 6 example, libboost_regex-gcc34-mt-d-1_36.a, doesn't seem to be present in my system. So, it looks like something was not right with the building of this library. What can I do to ensure that the library, libboost_regex-gcc34-mt-d-1_36.a, is made. Thank You, John

1 0

[Serialization] archive_exception from bad interaction serialization() and load_construct_data()
by Boylan, Ross 14 Jun '21

14 Jun '21

In short, combining a class implementation of serialize() with load/save_construct_data as described in the docs writes and reads data twice. Varying the pattern can produce exceptions. My solution is to implement serialize() as a no-op and provide paired load/save_construct_data() functions. Is that actually a solution? Is there a better way? The code at the bottom of this message yields Microsoft C++ exception: boost::archive::archive_exception at memory location 0x000000B8189AC300. When attempting to read in what was just written out. Debugging shows that code attempts to read in the object twice, first in the class-specific load_construct_data function I wrote, and then again in the instance method A::serialize. Since the save operation only wrote it out once, there is nothing, or at least nothing expected, to read and things go badly. The documentation (https://www.boost.org/doc/libs/1_76_0/libs/serialization/doc/serialization.…) says "If there is no such default constructor, the function templates load_construct_data and perhaps save_construct_data will have to be overridden." "perhaps" seems to imply that it is not essential to do so, and since the lack of a default constructor only matters when materializing an object I only wrote a load_construct_data function. The example in the documentation does show both a save_construct_data and a load_construct_data function and if I uncomment save_construct_data in the code below, it runs without error and reconstructs the object. HOWEVER, this only works because the data are written out twice, and then read in twice. I think the problem is that TestBed.exe!boost::archive::detail::pointer_iserializer<boost::archive::text_iarchive,A>::load_object_ptr(boost::archive::detail::basic_iarchive & ar, void * t, const unsigned int file_version) Line 340 at J:\Programs\boost_1_76_0\boost\archive\detail\iserializer.hpp(340) first materializes the object and then--after it is already constructed--passes it off to ar_impl >> boost::serialization::make_nvp(NULL, * static_cast<T *>(t)); at the end, triggering the call to A::serialize and the 2nd read from the archive. For now I have kept the save_construct_data function and made A::serialize a no-op; the serialization framework seem to require that it exist. This appears to work. Boost 1.76 Microsoft Visual Studio Community 2019 v16.10.1 with Language Level /std:c++latest. // TestBed.cpp : This file contains the 'main' function. Program execution begins and ends there. // #include <iostream> #include <fstream> #include <string> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> class A : boost::noncopyable { public: int a1; A(const int x1) : a1(x1) {}; virtual ~A() {}; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar& a1; }; }; namespace boost { namespace serialization { #if 0 template<class Archive> void save_construct_data(Archive& ar, const A* pa, const unsigned int version) { ar& pa->a1; }; #endif template<class Archive> inline void load_construct_data(Archive& ar, A* pa, const unsigned int file_version) { int x1; ar >> x1; ::new(pa)A(x1); } } } /* these are separate functions partly so RAII will close files*/ void write_out(const std::string& fpath, const A& a) { std::ofstream ofs(fpath); boost::archive::text_oarchive oa(ofs); oa << &a; } A* read_in(const std::string& fpath) { A* pa; std::ifstream ifs(fpath); boost::archive::text_iarchive ia(ifs); ia >> pa; return pa; } int main(int argc, char** argv) { const std::string fname("test.srl"); A a(810); write_out(fname, a); A* aa = read_in(fname); std::cout << "A(" << aa->a1 << std::endl; return 0; }

1 1

[Boost::asio] How to set the name of work_scheduler thread started by boost::asio?
by Marco Guest 09 Jun '21

09 Jun '21

Hello, I'm looking to set custom names to std::threads started indirectly when using boost:asio library (on Linux operating system). I have seen this stack trace for such thread by gdb: pthread_cond_wait () from /lib64/libpthread.so.0 void boost::asio::detail::posix_event::wait<boost::asio::detail::conditionally_enabled_mutex::scoped_lock>(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&) ()2 boost::asio::detail::conditionally_enabled_event::wait(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&) () boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) () boost::asio::detail::scheduler::run(boost::system::error_code&) () boost::asio::detail::resolver_service_base::work_scheduler_runner::operator()() () boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_scheduler_runner>::run() () boost_asio_detail_posix_thread_function () start_thread () from /lib64/libpthread.so.0 clone () from /lib64/libc.so.6 Setting names would be useful to debug my application behaviour in high throughput conditions and to be able to easily check the CPU usage of each thread using “top –H”. Is there a way to do so? Thanks

1 0

[QUESTION] what's meaning of boost::asio::require()?
by ZheNing Hu 06 Jun '21

06 Jun '21

Hi, I ran into difficulties when I was reading boost::asio http server example[1], I see: work_.push_back( boost::asio::require(io_context->get_executor(), boost::asio::execution::outstanding_work.tracked)); I don't know what is the meaning of this code? Or what is boost::asio::require()? I did not find useful information to introduce it. [1] https://www.boost.org/doc/libs/1_76_0/doc/html/boost_asio/example/cpp03/htt… -- ZheNing Hu

2 1

[Parameter Library] How to define a constexpr function
by pavel b 04 Jun '21

04 Jun '21

Hi all, Is it possible to define a constexpr function using BOOST_PARAMETER_FUNCTION? what is the correct syntax? Best regards, P

1 0

WinDbgCached_exe recognize has threat by Bitdefender
by Mauro Ziliani 01 Jun '21

01 Jun '21

Hi all. I build boost 1.76.0 woth Visual Studio 2019. I try to scan my pc with bitdefender (free version). Bitdefender discover a threat in boost_1_76_0\bin.v2\stacktrace\build\msvc-142\release\address-model-32\link-static\threading-multi\WinDbgCached_exe.exe. The threat is recognized as Gen:Variant.Fugrafa.139255 Any idea about? Best regards, MZ Sent from Mailspring (https://getmailspring.com/) the best free email app for work

2 1

OpenSSL 3.0 support in boost.asio
by Gehrs, Volker 31 May '21

31 May '21

Hi all, Will boost.asio add support for OpenSSL 3.0 as soon as it is officially available? Do you have already some very rough date in mind when this can be the case. I know OpenSSL 3.0 has not been released, yet. Maybe it can be expressed as X Month after OpenSSL 3.0 release... My understanding is that OpenSSL 3.0 is a big architectural change. Can I expect that this change will have big impact on the usage of boost.asio as well? Thanks and best regards! Volker

1 0

Build issue utilizing Boost::regex
by Brad Smith 29 May '21

29 May '21

Hi, I am trying to upgrade from Boost 1.73 to Boost 1.76 and down to only one consumer left that will not build. This appears to be an issue with Boost::regex. I noticed this in the Boost 1.76 release notes.. "Regex is now header only except in C++03 mode." Clang defaults to C++14, but I noticed BOOST_REGEX_CXX03 is defined. The project does not specify a particular C++ version so it should be using C++14. The functions below exist in the Boost 1.73 Boost::regex library but not in the 1.76 library. The project in question uses the function regex_match(). Any hints as to how to resolve this? ld: error: undefined symbol: boost::scoped_static_mutex_lock::scoped_static_mutex_lock(boost::static_mutex&, bool) >>> referenced by Config.cpp >>> � Config.o:(boost::object_cache<boost::re_detail_500::cpp_regex_traits_base<char>, boost::re_detail_500::cpp_regex_traits_implementation<char> >::get(boost::re_detail_500::cpp_regex_traits_base<char> const&, unsigned long)) >>> referenced by Config.cpp >>> � Config.o:(boost::cpp_regex_traits<char>::get_catalog_name()) >>> referenced by Config.cpp >>> � Config.o:(boost::re_detail_500::save_state_init::~save_state_init()) >>> referenced 2 more times ld: error: undefined symbol: boost::scoped_static_mutex_lock::~scoped_static_mutex_lock() >>> referenced by Config.cpp >>> � Config.o:(boost::object_cache<boost::re_detail_500::cpp_regex_traits_base<char>, boost::re_detail_500::cpp_regex_traits_implementation<char> >::get(boost::re_detail_500::cpp_regex_traits_base<char> const&, unsigned long)) >>> referenced by Config.cpp >>> � Config.o:(boost::object_cache<boost::re_detail_500::cpp_regex_traits_base<char>, boost::re_detail_500::cpp_regex_traits_implementation<char> >::get(boost::re_detail_500::cpp_regex_traits_base<char> const&, unsigned long)) >>> referenced by Config.cpp >>> � Config.o:(boost::cpp_regex_traits<char>::get_catalog_name()) >>> referenced 5 more times c++: error: linker command failed with exit code 1 (use -v to see invocation)

2 2

[locale] Boost.Locale cannot be used with std::regex
by Josue Andrade Gomes 24 May '21

24 May '21

It seems that Boost.Locale cannot be used with std::regex. See the code below: #include <regex> #include <boost/locale.hpp> int main() { try { boost::locale::generator gen; std::locale de_DE(gen("de_DE.UTF-8")); std::wstring in(L"Grün GRÜN grün"); std::wregex rx; rx.imbue(de_DE); rx.assign(L"grün", std::regex::icase); std::wcout << std::regex_replace(in, rx, L"green") << L"\n"; } catch (std::exception &e) { std::cout << "Exception: " << e.what() << "\n"; } } Outputs: green GRÜN green However this: #include <regex> #include <locale> int main() { try { std::locale de_DE("de_DE.UTF-8"); std::wstring in(L"Grün GRÜN grün"); std::wregex rx; rx.imbue(de_DE); rx.assign(L"grün", std::regex::icase); std::wcout << std::regex_replace(in, rx, L"green") << L"\n"; } catch (std::exception &e) { std::cout << "Exception: " << e.what() << "\n"; } } Correctly outputs: green green green Tested on Ubuntu 20.04.2. g++ 10.2, Boost.Locale built with ICU support using vcpkg (thus static link).

1 0