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

Toolset version for Visual Studio 2017 15.6.3
by Chris Stankevitz 10 Apr '18

10 Apr '18

What version should I pass to b2 --toolset=msvc-x.y for "Visual Studio 2017 15.6.3"? [1] says [2] will have an up-to-date list with an answer, but [2] is not up-to-date. Thank you, Chris [1] https://www.boost.org/doc/libs/1_65_1/more/getting_started/windows.html#ide… [2] https://www.boost.org/build/doc/html/bbv2/reference/tools.html

4 4

[asio] SSL async_shutdown() never finishes if called when async_read_some() is in progress
by Alexander D. 08 Apr '18

08 Apr '18

Hello, I'm writing a middleware which basically adds an SSL layer to the connection between a client and a server. The connection is bidirectional, so I need to read from each side and write to the other. The client can also close the connection at any time, in which case async_shutdown() must be called on the server's stream. The problem is, often the shutdown happens when the program is waiting on the server through async_read_some(), and the shutdown will never finish. The following code illustrates this issue: #include <iostream> #include <boost/asio.hpp> #include <boost/asio/ssl.hpp> int main(int argc, char* argv[]) { try { boost::asio::io_context io_context; boost::asio::streambuf buffer; boost::asio::ssl::context ctx(boost::asio::ssl::context::tlsv12); ctx.set_verify_mode(boost::asio::ssl::verify_none); boost::asio::ssl::stream<boost::asio::ip::tcp::socket> sock(io_context, ctx); sock.next_layer().connect(boost::asio::ip::tcp::endpoint( boost::asio::ip::make_address("127.0.0.1"), 4433)); sock.handshake(boost::asio::ssl::stream_base::client); /* "async_shutdown" won't appear unless async_read_some() * is commented out */ sock.async_read_some(buffer.prepare(1024), [](boost::system::error_code, size_t) {std::cout << "async_read_some" << std::endl;}); sock.async_shutdown([](boost::system::error_code) {std::cout << "async_shutdown" << std::endl;}); io_context.run(); } catch (std::exception& e) { std::cerr << "Exception: " << e.what() << "\n"; } return 0; } To reproduce, start up an SSL server: openssl genrsa -out key.pem 2048 openssl req -new -sha256 -key key.pem -out csr.csr openssl req -x509 -sha256 -days 365 -key key.pem -in csr.csr -out server.pem openssl s_server -key key.pem -cert server.pem and run the program. Notice that "async_shutdown" does not finish even if the server is killed. In practice, this leaks the memory of the shutdown handler and whatever is bound to it. The only solution I can think of would be to cancel the read operation, but there's no portable way in asio to do this. Can someone point out how to solve this? Cheers, Alexander

5 11

[release] Boost 1.67.0 Beta 1
by Daniel James 07 Apr '18

07 Apr '18

Boost release 1.67.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/> The SHA256 checksums are as follows: 154cf490da858fd9c2307bb904b07a42cbe8355ecf99d5477f0d843c6d03cdda boost_1_67_0_b1.7z 0d854b208fefaeb5837d6c417f505b189275e32d017f6226001fb165a5ac51ed boost_1_67_0_b1.tar.bz2 6eb3f9ca8db355765f41361e1e26976228f0c2dff400aade8a5e97aec6aa59f4 boost_1_67_0_b1.tar.gz 678a6459f2517932536ec97297be1de46ea073f2e2ee17ec8397b80aa0953f49 boost_1_67_0_b1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_67_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

9 14

Pointer Container Library changes in 1.66.0
by Kevin Hardman 06 Apr '18

06 Apr '18

I am seeing changes in the Pointer Container Library that are preventing my existing application from compile. I see no notice of changes in the 1.66.0 release notes <http://www.boost.org/users/history/version_1_66_0.html <http://www.boost.org/users/history/version_1_66_0.html>>. Is there documentation on the changes and what is required to migrate existing users to the new library? —kevin

5 10

[log] Unable to use own severity struct encapsulated in namespace
by Sebastian Messerschmidt 06 Apr '18

06 Apr '18

Hi folks, When taking this example [1] and modifying the enum 'severity_level' like this: namespace x { struct test { enum severity_level { normal, notification, warning, error, critical }; }; } and replacing all references to severity_level with the appropriate x::test::severity_level the 'operator<<' overload for the severity_level is not issued. Can anyone help me with this one? I can supply the complete modified example if needed Cheers Sebastian [1] https://www.boost.org/doc/libs/1_58_0/libs/log/example/doc/tutorial_attribu…

2 4

[ptr_map] Warning about returning address of local variable
by Bill Buklis 05 Apr '18

05 Apr '18

I'm not sure if this a potential bug/problem or just a benign warning, but when using the map_values range adaptor with a ptr_map container I get a warning about returning an address of a local variable. It seems benign as the expected processing happens, but this type of warning generally doesn't sound like a good thing. The following useless code will trigger it. #include <boost/ptr_container/ptr_map.hpp> #include <boost/range/algorithm.hpp> #include <boost/range/adaptors.hpp> struct sample { int value; }; typedef boost::ptr_map<int, sample> themap; int main() { themap data; int key = 5; data.insert(key, new sample); boost::for_each(data | boost::adaptors::map_values, [](sample* s) { s->value = 10; }); return 0; } I'm using Visual Studio 2017. I also have conformance mode (/permissive-) turned on for stricter language compliance in case it makes a difference. As an aside, I was a little surprised when trying out this little sample that the inclusion of the above headers is enough to require linking with the boost regex library. I figure it's probably a reference in the adaptors somewhere. It's not a big deal. These lib files are normally available anyway. -- Bill

2 1

boost::asio::async_read_until fills streambuf less than actually received
by David Demelier 03 Apr '18

03 Apr '18

Hello, I'm using Asio to read IRC messages asynchronously from a server. I use boost::asio::async_read_until with "\r\n" as delimiter and a boost::asio::streambuf as output buffer. I mostly implemented the code like described on my original question/answer here: https://stackoverflow.com/questions/40561097/read-until-a-string-delimi ter-in-boostasiostreambuf I sometimes get the bytes_transferred argument bigger that what is filled into the buffer. My code looks like this: void connection::do_recv(handler_t handler) { boost::asio::async_read_until(socket_, buffer_, "\r\n", [this, handler] (auto code, auto xfer) { if (code || xfer == 0U) handler(std::move(code), message()); else { //assert(buffer_.size() > xfer); std::cout << "xfer: " << xfer << std::endl; std::cout << "size: " << buffer_.size() << std::endl; std::string str( boost::asio::buffers_begin(buffer_.data()), boost::asio::buffers_begin(buffer_.data()) + xfer - 2 ); buffer_.consume(xfer); handler(std::move(code), message::parse(str)); } }); } void connection::rflush() { if (input_.empty()) return; do_recv([this] (auto code, auto message) { auto h = input_.front(); // Delete first, in case of exceptions. input_.pop_front(); if (h) h(code, std::move(message)); if (!code) rflush(); }); } void connection::recv(handler_t handler) { auto in_progress = !input_.empty(); input_.push_back(std::move(handler)); if (!in_progress) rflush(); } For some reasons, after several calls, I get an assertion failure in the std::string construction. Because buffer_.size() is actually smaller than xfer. I could not understand why. Example of output: ... ... xfer: 87 size: 141 Note: I've implemented the recv() public function like what I can see for send in some tutorials. I wanted a queue of handlers so I can safely call recv() multiple times before first functions finished completely. Regards, -- David

2 1

Crossbuilding for ARM
by Mats Webjörn/WIKAB 30 Mar '18

30 Mar '18

I'm trying to build for ARM, and have some problems in making b2 find user-config.jam when it's located outside boost root dir. First I go to boost/tools/build and run ./b2 install -prefix=/home/administrator/project/myproj/build/boost Then I run ./b2 toolset=gcc-arm --build-dir=/home/administrator/project/myproj/build/boost stage According to http://www.boost.org/build/doc/html/bbv2/overview/configuration.html Boost.Build<http://www.boost.org/build/doc/html/bbv2/overview/configuration.html%20Boos…> will search $HOME and $BOOST_BUILD_PATH, but if I add --debug-configuration to b2 command then I can see that it searches '/home/administrator' = $HOME '/home/administrator/project/myproj/externals/boost/tools/build/src/kernel' '/usr/share/boost-build' '/home/administrator/project/myproj/externals/boost/tools/build/src/kernel' '/home/administrator/project/myproj/externals/boost/tools/build/src/util' '/home/administrator/project/myproj/externals/boost/tools/build/src/build' '/home/administrator/project/myproj/externals/boost/tools/build/src/tools' '/home/administrator/project/myproj/externals/boost/tools/build/src/contrib' '/home/administrator/project/myproj/externals/boost/tools/build/src/.'. Where none of the directories searched is the one I've provided as buid directory. It seems odd that $BOOST_BUILD_PATH should be "the one in the top-level directory of your Boost.Build installation" since http://www.boost.org/build/doc/html/bbv2/overview/invocation.html describes --build-dir as "the build directories for all project roots being built". It seems like the documentation isn't correct. I'm just not sure which one is right and which is wrong. Has anyone crossbuilt for ARM on Linux? Regards Mats Webjörn E-Mail: konsult(a)webjorn.com Webjörn IngenjörsKonsult AB Tel +46 8 584 238 80 Solhemsbackarna 75A Fax +46 8 445 69 21 SE-163 56 SPÅNGA Mobil +46 70 639 16 99 Sweden

1 0

[Boost::Test] short form of catch_system_errors not working
by Konstantin Kivi 30 Mar '18

30 Mar '18

Occasionally I need a core dump if testing goes wrong. Boost test have the following option ------------ Parameter: catch_system_errors Allows to switch between catching and ignoring system errors (signals). Command line formats: --[no_]catch_system_errors[=<boolean value>] -s[ <boolean value>] ------------------- I never managed to get short options to work and has to search for a long option exact name. Neither '-s no', '-s false' , -sno with or without quotes are not accepted. examples ----- $ test_app -s no Boost.Test WARNING: token "no" does not correspond to the Boost.Test argument and should be placed after all Boost.Test arguments and the -- separator. For example: test_app --random -- no ------ $ test_app "-s no" Invalid separator for the parameter catch_system_errors in the argument -s no ----- Is it a known bug? Best regards, Konstantin

2 1

[boost][interprocess] Need clarification on file_lock documentation
by Rob Conde 29 Mar '18

29 Mar '18

The documentation of boost::interprocess::file_lock has some cautions on synchronization limitations: * It's unspecified if a file_lock synchronizes two threads from the same process. * It's unspecified if a process can use two file_lock objects pointing to the same file. But then gives the guidance: * For each file, use a single file_lock object per process. * Use the same thread to lock and unlock a file. I then created the following example: <https://wandbox.org/permlink/dO2rRDCHVWBE3pGr>https://wandbox.org/permlink/3CNfkA3RcMkwbd2v #include <fstream> #include <iostream> #include <cstdlib> #include <boost/interprocess/sync/file_lock.hpp> #include <boost/interprocess/sync/scoped_lock.hpp> #include <boost/filesystem.hpp> #include <mutex> #include <thread> #include <chrono> int main() { std::ofstream("f.txt"); boost::interprocess::file_lock lock("f.txt"); std::mutex mtx; const size_t max = 100; size_t t1Count = 0; std::thread t1 ( [&lock,&t1Count,&mtx,max]() { while(t1Count < max) { //std::lock_guard<std::mutex> mtxLock(mtx); boost::interprocess::scoped_lock<boost::interprocess::file_lock> guard(lock); std::cout << "Number 1" << std::endl; t1Count++; std::this_thread::sleep_for(std::chrono::milliseconds(1)); } } ); size_t t2Count = 0; std::thread t2 ( [&lock,&t2Count,&mtx,max]() { while(t2Count < max) { //std::lock_guard<std::mutex> mtxLock(mtx); boost::interprocess::scoped_lock<boost::interprocess::file_lock> guard(lock); std::cout << "Number 2" << std::endl; t2Count++; std::this_thread::sleep_for(std::chrono::milliseconds(1)); } } ); t1.join(); t2.join(); return 0; } It only works properly if the std::mutex is used in addition to the file_lock. That was originally my thought when I read "It's unspecified if a file_lock synchronizes two threads from the same process.", but it seemed like I was following the guidance "Use the same thread to lock and unlock a file.". If I haven't messed anything up, I would probably update the documentation to say something like: "If utilitizing the file_lock from multiple threads within the same process, synchronize access to the file_lock with an intraprocess synchronization mechanism such as a mutex." Otherwise, is it a bug? Thanks, Rob

1 0