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

(no subject)
by Dk Jack 18 Feb '21

18 Feb '21

Hi, I am using boost 1.58 in my project. Ran into a crash in the boost filesystem library. I've included the relevant stack trace at the end of the email. My code is something like this: boost::filesystem::path fpath(mFilename.c_str()); if (!boost::filesystem::exists(fpath)) { // log a message and return. return; } auto curr_time = boost::filesystem::last_write_time(fpath); <== crash The crash is not consistent and happened randomly. I tested the above code in a small test program with just the above code. I made the input file unreadable etc, even then it was able to successfully read the last write timestamp of the file without any issues. Not sure why this particular call would throw an error. Since it's compiled with -O2, the error code is optimized out in the stack trace. Any ideas? Thanks for your help. Dk. (gdb) bt #0 0x00007f01651ba387 in raise () from /lib64/libc.so.6 #1 0x00007f01651bba78 in abort () from /lib64/libc.so.6 #2 0x00007f0160d087d5 in __gnu_cxx::__verbose_terminate_handler() () from /lib64/libstdc++.so.6 #3 0x00007f0160d06746 in ?? () from /lib64/libstdc++.so.6 #4 0x00007f0160d06773 in std::terminate() () from /lib64/libstdc++.so.6 #5 0x00007f0160d06993 in __cxa_throw () from /lib64/libstdc++.so.6 #6 0x00007f0161171f5f in boost::filesystem::detail::last_write_time(boost::filesystem::path const&, boost::system::error_code*) () from xxx.so #7 0x00007f0161089657 in last_write_time (p=...) at /usr/local/include/boost/filesystem/operations.hpp:594

2 1

Boost cannot find numpy37 on Dockerized Ubuntu 20.04
by Roy de Bokx 17 Feb '21

17 Feb '21

Hi there, I've been trying to get GP-GOMEA running in a dockerized environment <https://github.com/marcovirgolin/GP-GOMEA/issues/2>, which is a project that is built using Boost. As part of the build process, the source code is compiled by the g++ compiler, using the flag -lboost_numpy37, which fails because (it seems) numpy cannot be found. I've reported this also as an issue also in the boost repository <https://github.com/boostorg/boost/issues/462>, but mclow advised me to send this to the boost-users mailinglist too. I've create the following Dockerfile as a minimal test case, which runs into the same problem. I'm a bit of a noob when it comes to Boost and numpy, but from what I found so far on the web, this should work (but it doesn't) FROM ubuntu:20.04 ENV DEBIAN_FRONTEND noninteractive RUN apt-get update && apt-get upgrade -y && apt-get clean RUN apt-get install -y curl python3.7 python3-dev python3-distutils python3-numpy # Install latest boost version RUN apt-get -y install wget g++ RUN wget https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2 && \ tar --bzip2 -xf boost_1_75_0.tar.bz2 && \ cd boost_1_75_0 && \ # this will generate ./b2 ./bootstrap.sh --prefix=/usr/local && \ ./b2 --with=all install && \ sh -c 'echo "/usr/local/lib" >> /etc/ld.so.conf.d/local.conf' && \ ldconfig # Check numpy installation RUN find / -name "numpy.hpp" RUN find / -name "libboost_numpy37.so" RUN find / -name "libboost_numpy3.so" RUN find / -name "libboost_numpy.so" RUN ld -lboost_numpy37 --verbose This eventually results in the following error: The command '/bin/sh -c ld -lboost_numpy37 --verbose' returned a non-zero code: 1, because it could not find any libboost_numpy37.so or libboost_numpy37.o file. The full logs are attached in the GH issue linked above. Did anyone encounter something similar, or does anyone have an idea what could cause this? Any help is much appreciated! -Roy

2 2

How to change read/write method of source/sink device in C++ boost::iostreams?
by mostaan fereidooni 16 Feb '21

16 Feb '21

I'm trying to get familiar with boost::iostream, so in a example program I'm writing, I want to read a text from a file and write it to file. I would use my inherited class from file_source/file_sink as device to read/write. In the read method, my class needs to add each character with one and write method needs to subtract one from each character. First of all, I want to make sure that the reading part of the program works properly so you can see the code as follow: #include <boost/iostreams/stream.hpp>#include <fstream>#include "MyFileSource.h"#include <iostream>using namespace std;using namespace boost::iostreams;int main(){ MyFileSource<char> fileSource("source.txt"); stream<MyFileSource<char>> myStream(fileSource); std::cout << myStream.rdbuf(); fileSource.close(); } and my inherited source device code is as follow: template <typename charType>class MyFileSource : public boost::iostreams::file_source {public: MyFileSource(const std::string& path) : boost::iostreams::file_source(path) { file_path = path; if (!is_open()) open(path); seek(0, ios::end); sizeOfFile = seek(0, ios::cur); seek(0, ios::beg); buffer = new charType[sizeOfFile]; } std::streamsize read(charType*, std::streamsize) { std::streamsize readCount = boost::iostreams::file_source::read(buffer, sizeOfFile); if (readCount > 0) { std::string result(buffer, readCount); for (char& c : result) c++; finalResult = result; } return readCount; } private: string file_path; int sizeOfFile; charType* buffer; std::string finalResult; }; unfortunately, the result of *std::cout << myStream.rdbuf()* with above read method is nothing while if I delete the read method of MyFileSource class to use the read method of parent, the result will be correct. Any help will be appreciated.

1 0

How to link boost library DLLs?
by Anand Arumugam 14 Feb '21

14 Feb '21

Hello all, How to properly link boost library DLLs? I have #define-d the following: #define BOOST_ALL_DYN_LINK #define BOOST_DYN_LINK #define BOOST_THREAD_USE_DLL #define BOOST_THREAD_PROVIDES_FUTURE_CONTINUATION #define BOOST_THREAD_VERSION 4 And I still get the following problem: --------------------------- testprogs.exe - System Error --------------------------- The code execution cannot proceed because boost_thread-vc142-mt-gd-x64-1_75.dll was not found. Reinstalling the program may fix this problem. --------------------------- OK --------------------------- I get the same error when I try to run the program using DLLs that I built and while running using the prebuilt binaries. Not sure what step I'm missing. The program runs fine if I build using static libs. The problem is only with DLLs. Any help is much appreciated. Thanks, Anand.

3 3

Boost.Asio as "thread-pool": How to apply back-pressure?
by Dominique Devienne 10 Feb '21

10 Feb '21

Hi, I'm using Boost.ASIO, not for networking, but simply to parallelize work items, with a simple graph of "processing nodes" as detailed below. It's working fine, but uses too much memory. I'd like insights on limiting memory use via "throttling", or what I've also seen called "back-pressure". At a high level, I process two files (A and B) composed of several "entries" each, extracting a subset or a transformation of those entries, that I then write into an output file (C). (those 3 files reach into the many GBs, thus the need for parallelism, and limiting memory use). Extracting entries from A and B are independent operations, implemented single-threaded, producing independent work items (for subsetting or transforming each item), A#1...A#n, and B#1..B#m. That's the "fan-out" part, with each work-item (task) scheduled on any thread of the ASIO pool, since independent. Writing to C is also single-threaded, and needs to "fan-in" the work posted by the A#n and B#m functors, and I serialize that via posting to a C-specific strand (still on any thread, as long as serialized, doesn't matter). Lets call all those tasks writing to C the C#n+m tasks, which are posted to the strand via the A#s and B#s. My issue is that Boost.Asio seems to schedule an awful lots of A# and B# tasks, before getting to the C# tasks, which results in accumulating in memory too many C# tasks, and thus using too much memory. I don't see a way to force more C "downstream" tasks to be scheduled, before processing so much A and B tasks, and accumulating pending C tasks in the work queue, thus using too much memory again. Could someone please recommend a way to have a more balanced flow of tasks in the graph? Or alternative designs even, if what I do above is not ideal. Is Boost.Asio even suitable in this case? Thanks, --DD

7 17

[boost-process] why does my child process not get EOF on stdin
by harald 01 Feb '21

01 Feb '21

Dear community, dear experts! I am trying to use boost::process to call weasyprint to convert HTML to a picture. To do that I wrote a test program (further down in the mail). This worked fine and did what i expected. But it stopped working as soon as I tried to convert two files at the same time by changing new renderer_t(io_context, "<head></head><body></body>"); in main to new renderer_t(io_context, "<head></head><body></body>"); new renderer_t(io_context, "<head></head><body></body>"); Now weasyprint hangs. I changed the call to weasyprint to weasyprint2, which is a short bash script for testing purposes: --------------------------------------------------------------------------------- #! /bin/bash cat > /dev/null echo "This should be a PNG picture" --------------------------------------------------------------------------------- It reads stdin until it gets EOF and then writes something to stdout before terminating. Same result. It seems that my program does not close stdin of the child, so it never gets EOF on stdin. But only when more than one child process is running at the same time. So obviously I am doing something wrong, but I have no idea what! Does anybody have a hint for me? I am on xubuntu 20.10 compiler is g++ (Ubuntu 10.2.0-13ubuntu1) 10.2.0, boost version 1.75.0 compiler command line (from my IDE): g++ -c main.cpp -g -O0 -Wall -Wextra -std=c++17 -o build-Debug/main.cpp.o -I. -I. --------------------------------------------------------------------------------- #include <boost/smart_ptr/intrusive_ptr.hpp> #include <boost/smart_ptr/intrusive_ref_counter.hpp> #include <boost/process.hpp> #include <boost/asio/write.hpp> #include <iostream> namespace bp = boost::process; bool is_eof( std::error_code error) { boost::system::error_code eof = boost::asio::error::eof; return error == eof; } struct renderer_t : public boost::intrusive_ref_counter<renderer_t> { using pointer = boost::intrusive_ptr<renderer_t>; boost::asio::io_context &io_context; const std::string html; bp::child child; bp::async_pipe in; bp::async_pipe out; bp::async_pipe err; std::array<unsigned char, 256> outbuf; std::array<char, 256> errbuf; std::vector<unsigned char> result; std::error_code result_error; std::string errmsg; ~renderer_t() { std::cout << "renderer_t::~renderer_t\n"; if (!errmsg.empty()) std::cerr << "renderer_t::~renderer_t: stderr: " << errmsg << "\n"; } renderer_t( boost::asio::io_context &io_context, const std::string &html) : io_context(io_context), html(html), in(io_context), out(io_context), err(io_context) { post( io_context, [self = pointer(this)]() { self->start(); }); } void start() { std::error_code ec; std::cout << "renderer_t::start\n"; bp::child c( "weasyprint2 -m screen -p -f png - /dev/stdout", bp::std_in < in, bp::std_out > out, bp::std_err > err, bp::on_exit=[self = pointer(this)]( int exit, std::error_code error) { self->on_exit(error, exit); }, bp::start_dir="/data/build/", io_context, ec); if (ec) { std::cerr << "renderer_t::start: creating child failed: " << ec.message() << "\n"; if (!result_error) result_error = ec; return; } child = std::move(c); boost::asio::async_write( in, boost::asio::buffer(html), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_write(error, bytes); }); out.async_read_some( boost::asio::buffer(outbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_out(error, bytes); }); err.async_read_some( boost::asio::buffer(errbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_err(error, bytes); }); } void on_write( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_write\n"; if (error) { std::cerr << "renderer_t::on_write: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } if (bytes != html.size()) { std::cerr << "renderer_t::on_write: short write\n"; } boost::system::error_code ec; in.close(ec); if (ec) { std::cerr << "renderer_t::on_write: close failed: " << error.message() << "\n"; } } void on_read_out( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_read_out\n"; if (is_eof(error)) { std::cout << "renderer_t::on_read_out: EOF\n"; return; } else if (error) { std::cerr << "renderer_t::on_read_out: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } else { result.insert( end(result), begin(outbuf), begin(outbuf) + bytes); out.async_read_some( boost::asio::buffer(outbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_out(error, bytes); }); } } void on_read_err( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_read_err\n"; if (is_eof(error)) { std::cout << "renderer_t::on_read_err: EOF\n"; return; } else if (error) { std::cerr << "renderer_t::on_read_err: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } else { std::string e(begin(errbuf), begin(errbuf) + bytes); std::cerr << "renderer_t::on_read_err: from stderr: " << e << "\n"; errmsg.insert( end(errmsg), begin(errbuf), begin(errbuf) + bytes); err.async_read_some( boost::asio::buffer(errbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_err(error, bytes); }); } } void on_exit( std::error_code error, int exit) { std::cout << "renderer_t::on_exit\n"; if (error) { std::cerr << "renderer_t::on_exit: error: " << error.message() << "\n"; if (!result_error) result_error = error; return; } if (exit) { std::cerr << "renderer_t::on_exit: weasyprint returned " << exit << "\n"; if (!result_error) result_error = make_error_code(std::errc::no_such_process); } } }; int main() { boost::asio::io_context io_context; bp::async_pipe in(io_context); new renderer_t(io_context, "<head></head><body></body>"); io_context.run(); return 0; } --------------------------------------------------------------------------------- Regards Harald

1 0

TOMS748 question
by Shriramana Sharma 29 Jan '21

29 Jan '21

Namaste. This is wrt the TOMS748 math root finding implementation: Given that `if(fa == 0)` is handled at: https://github.com/boostorg/math/blob/develop/include/boost/math/tools/toms… … and the function returns in case of the above condition, it is not clear to me what the need is for the `if (fa != 0)` at: https://github.com/boostorg/math/blob/develop/include/boost/math/tools/toms… Note that I do not find the condition being applied at the SciPy implementation of this algorithm at: https://github.com/scipy/scipy/blob/v1.6.0/scipy/optimize/zeros.py#L1220 Now I also note similar checks at: https://github.com/boostorg/math/blob/develop/include/boost/math/tools/toms… https://github.com/boostorg/math/blob/develop/include/boost/math/tools/toms… … but regarding those lines, while I can understand the need for checking there after more bracketing work is done, it is not clear to me why `(fa == 0)` is alone checked for, and not `(fb == 0)` as well. I would have thought the algorithm is not biased towards a or b. Indeed, in the last steps from: https://github.com/boostorg/math/blob/develop/include/boost/math/tools/toms…, … both the conditions are checked for, which is what I would expect even in the intervening steps. Now the lines seem to have originated in the very first commit implementing this algorithm: https://github.com/boostorg/math/commit/79a8199f9c26ba353fb52ec4543f75ffc2a… … but I do not see a way to contact the author jzmaddock other than posting to this list, so I hope someone/they see here and reply. Thanks! -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा 𑀰𑁆𑀭𑀻𑀭𑀫𑀡𑀰𑀭𑁆𑀫𑀸

2 7

Correct way to handle error in boost::filesystem::recursive_directory_iterator::increment()?
by Dominique Pellé 23 Jan '21

23 Jan '21

Hi I see code like this in an application to iterate over files in a directory with boost::filesystem (v1.70) without using exceptions: boost::filesystem::path dir("somedir"); boost::system::error_code error; boost::filesystem::directory_iterator node(dir, error), end; if (error) { return ...; } for (; node != end; node.increment(error)) { const boost::filesystem::path& path = node->path(); // ... } It appears to work... or mostly work since a crash was reported and the stack points to this area of the code. It's a rare crash that I could not reproduce myself. I suspect that there is a bug in the above code and it should instead be: boost::filesystem::path dir("somedir"); boost::system::error_code error; boost::filesystem::directory_iterator node(dir, error), end; for (; !error && node != end; node.increment(error)) { const boost::filesystem::path& path = node->path(); // ... } In other words, I suspect that we need to check that node.increment(error) in the for loop did not give an error before checking the condition "node != end", or else we may enter the loop in case of error and then it may access node->path() with an invalid node iterator. I could not find in the doc at ... https://www.boost.org/doc/libs/1_75_0/libs/filesystem/doc/reference.html ... what exactly happens when node.increment(error) gives an error. Perhaps the doc deserves clarification or an example illustrating how to reliably iterate over files without using exceptions would be welcome. Thanks Dominique

1 1

Serialization and static Libraries
by Wolfgang Meyerle 20 Jan '21

20 Jan '21

Hi, probably has been asked already thousand of times but I'm stuck currently with some code: Assuming I have the following files (The Base class Action is serialized in the same way): File: Ping.h #include"Action.h" classPing:publicAction{ public: voidoperator()(); Ping(); Ping*clone()const; ~Ping(); template<typenameArchive> voidserialize(Archive&ar,constunsignedint); }; BOOST_CLASS_EXPORT_KEY2(Ping,"Ping"); File: Ping.cpp #include"Ping.h" #include<iostream> #include<boost/serialization/base_object.hpp> #include<boost/serialization/export.hpp> #include<boost/serialization/tracking.hpp> #include"Action.h" #include"system.h" #include"pong.h" #include"serializerdeserializer.h" #include"system.h" #include"connection.h" #include"communication.h" voidPing::operator()(){ } Ping::Ping() { } Ping*Ping::clone()const{ Ping*ping=newPing(*this); returnping; } template<typenameArchive> voidPing::serialize(Archive&ar,constunsignedint){ ar&BOOST_SERIALIZATION_BASE_OBJECT_NVP(Action); } Ping::~Ping(){} BOOST_CLASS_EXPORT_IMPLEMENT(Ping); BOOST_CLASS_TRACKING(Ping,boost::serialization::track_never); If I now compile the project into a library. And link this library to a different project. If I try to serialize the class now it doesn't work. I get the following error: unregistered class - derived class not registered or exported According to the boost documentation I need to use BOOST_CLASS_EXPORT_KEY in the header file and BOOST_CLASS_EXPORT_IMPLEMENT in the corresponding cpp file. What did I miss? Regards, Wolfgang

1 0

[Boost-MPI][Boost-ODEINT] Running odeint within MPI-context without using mpi_state
by Roland Richter 19 Jan '21

19 Jan '21

Hei, I am currently using the odeint-solver for calculating the right hand side of a non-linear equation. For speeding up the calculation of the right hand side, I decided to test the MPI-implementation. Now, after I would prefer to keep the code backwards compatible, I did not want to replace state_type with mpi_state, and instead split up the initial vector by hand before calling odeint without telling odeint that I am operating within an MPI context. I take care of all communications which involve the vectors, and therefore I assumed that this approach should work (especially after it worked correctly in small test programs). Nevertheless, I encountered the issue that after a certain amount of steps the step size between the different threads starts to differ by a small amount, even though I am in the same iteration. As example: step number rank step size n 1 0.00025 n 0 0.00025 //Ok n + 1 1 0.00051152 n + 1 0 0.000511523 //Not ok I checked my program with valgrind for possible memory leaks/corruption which could overwrite something, but nothing relevant came up. The problem is repeatable. Therefore, is the general idea correct at all, or am I doing something wrong here by neglecting a possible communication between the different threads within odeint? Thanks! Regards, Roland

2 2