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

container: static_vector and type traits
by MM 15 Mar '22

15 Mar '22

Hello Should static_vector be of standard layout and/or trivially copyable? depending on the element type I see this outputs false std::cout << std::is_standard_layout_v<boost::container::static_vector<char,32>> << std::endl; std::cout << std::is_trivially_copyable_v<boost::container::static_vector<char,32>> << std::endl; Rds,

1 0

Boost.ASIO SSL Version?
by Osman Zakir 10 Mar '22

10 Mar '22

What version of OpenSSL does Boost.ASIO use? And may I suggest to consider upgrading to the latest version if that hasn't been done already (if it's not too much trouble)? I tried to use version 3.0.1 (LibreSSL 3.4 is already out but according to openssl.org, their official latest version is 3.0.1? I'm not sure.) with this project of mine: https://github.com/DragonOsman/currency_converter and got these errors: " 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\error.ipp(43,28): error C4996: 'ERR_func_error_string': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(54,29): error C4996: 'RSA_free': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(60,28): error C4996: 'DH_free': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(962,29): error C4996: 'd2i_RSAPrivateKey_bio': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(965,29): error C4996: 'PEM_read_bio_RSAPrivateKey': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(978,13): error C4996: 'SSL_CTX_use_RSAPrivateKey': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(1056,9): error C4996: 'SSL_CTX_use_RSAPrivateKey_file': Since OpenSSL 3.0 1>C:\local\boost_1_78_0\boost\asio\ssl\impl\context.ipp(1122,23): error C4996: 'PEM_read_bio_DHparams': Since OpenSSL 3.0 " Or should I stick to version 1.1.1m? Thanks for any replies.

2 3

Vertical slopes and Cubic Hermite Interpolation
by Cory Riddell 08 Mar '22

08 Mar '22

I'm reading about boost::math::interpolators::cubic_hermite and the constructor takes three arguments: x values, y values and slopes (dy/dx). Can this library be used when the slope at a point is vertical? If so, how do you specify that? I tried std::numeric_limits<double>::infinity() but that doesn't work. Cory

1 0

[Boost.Serialization] Exception during serialization through base pointer DLL & EXE
by Marc Viala 07 Mar '22

07 Mar '22

Hi, On our platform (VS2019, Windows x64, Boost 1.77) an exception occurs during the serialization of an instance through its base pointer. This error is systematic and I was able to reproduce w/ a minimal use test (cf. enclosed archive). This use case includes a solution w/ a DLL project and EXE project. The EXE project is a simple unit-test. On my platform when I execute the executable, I trigger an exception from Boost.Serialization ("unregistered void cast class cpe::derived_t<-class cpe::object_t"). I tried every recommandation that we can find on SO and Boost mailing lists without success. To be accurate, I prefer to mention that we are using Boost.Serialization Static Library flavor. Any help would be appreciated. -- Marc Viala

2 3

Re: [Boost-users] Boost SSL handshake(http_server_sync_ssl) : still reachable memory keeps increasing
by Sandeep Bhardwaj 04 Mar '22

04 Mar '22

Hi, I tried the async program as suggested and I still see one of the stacks where the "still reachable" memory keeps increasing with duration. I have attached the relevant stack and the program. Sorry I had to resend this email multiple times due to size limitations. Hopefully this will go through. On Fri, 4 Feb 2022 at 12:28, Sandeep Bhardwaj <sandybharblore(a)gmail.com> wrote: > Thanks a lot. I will give it a try. > > On Thu, 3 Feb 2022 at 23:15, Vinnie Falco <vinnie.falco(a)gmail.com> wrote: > >> On Thu, Feb 3, 2022 at 9:41 AM Sandeep Bhardwaj via Boost-users >> <boost-users(a)lists.boost.org> wrote: >> > http_server_sync_ssl.cpp >> >> Oh, right. Synchronous APIs have no way to time out. So if the remote >> host does not close gracefully (i.e. just slams the connection shut) >> then you will be left with a connection object which either has no way >> to be destroyed, or has to wait what could be a very long time (up to >> 2 hours) for the operating system to time out the synchronous read. >> >> Please try the asynchronous example, http_server_async_ssl.cpp and >> determine if the problem persists. >> >> Thanks >> >

2 6

Test post - please ignore
by Marshall Clow 02 Mar '22

02 Mar '22

I’ve got a report that posts to the lists are failing… Testing.

2 1

Boost::coroutine2 and compiling for ASAN problems
by tjisana (泰志) 16 Feb '22

16 Feb '22

Team, I'm trying to get a simple coroutine2 program to work with address sanitizer and I'm running into a block. I'm building boost_1_78_0 as follows: ./b2 context-impl=ucontext and compiling with -DBOOST_USE_ASAN and -DBOOST_USE_CONTEXT. I've built and rebuilt the library thinking I've made an error somewhere and it boils down to jump_fcontext and make_fcontext. What am I doing wrong/missing? Cheers, TJ g++ -DBOOST_USE_ASAN -DBOOST_USE_UCONTEXT -I/home/tjisana/Downloads/boost_1_78_0 -O0 -g3 -fsanitize=address -pedantic -Wall -c -fmessage-length=0 -o src/Testbed II.o ../src/Testbed II.cpp g++ -L/home/tjisana/Downloads/boost_1_78_0/stage/lib -fsanitize=address -o Testbed II src/Testbed II.o -lboost_context -lboost_coroutine /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /home/tjisana/Downloads/boost_1_78_0/stage/lib/libboost_coroutine.so: undefined reference to `jump_fcontext' /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /home/tjisana/Downloads/boost_1_78_0/stage/lib/libboost_coroutine.so: undefined reference to `make_fcontext' collect2: error: ld returned 1 exit status #include <queue> #include <memory> #include "boost/coroutine2/coroutine.hpp" typedef boost::coroutines2::coroutine<int> coro_t; int main() { int l = 0; std::queue<int> y({1,2,3,4}); std::queue<std::unique_ptr<int>> w; coro_t::push_type sink([&](coro_t::pull_type& source) { for (const auto& i : source) { while (!w.empty()) { auto ptr = std::move(w.front()); w.pop(); if (*ptr == 1) { std::cout << "first: " << i << std::endl; auto item = 21; w.push(std::move(std::make_unique<int>(item))); } else if (*ptr == 21) { std::cout << "second: " << i+2*i << std::endl; auto item = 32; w.push(std::move(std::make_unique<int>(item))); } else if (*ptr == 32) { std::cout << "third: " << i*i << std::endl; } } } source(); }); while (!y.empty()) { if (!y.empty()) { l = y.front(); y.pop(); w.push(std::move(std::make_unique<int>(1))); sink(l); } } return 0; }

3 3

std::launder and its usage in Boost
by Mikhail Kremniov 16 Feb '22

16 Feb '22

Hi, I wonder, what is the Boost community's opinion of std::launder? In particular, of its necessity when accessing an object that was created via placement-new in an aligned_storage. As I can see, it's used by Boost.Beast in its implementation of the variant type, but not in other parts of Boost. The reason I'm asking this is that I'm working on a C++14 code-base that uses Boost.Variant and Boost.Optional extensively (as well as other parts of Boost that use Variant and Optional internally). Now we're trying to switch to C++17 at least, and I worry whether it could potentially break things. To put things into context, C++ standard states in the [basic.life] section that if you had an object and then created a new one in the same location, you can use the pointer to the old object to refer to the new one only if (among other things) "the new object is of the same type as the original object (ignoring the top-level cv-qualifiers)". This means, as I understand it, that it's technically illegal to reinterpret_cast the pointer to aligned_storage to the pointer to the actual type of the object created via placement-new, because placement-new has already ended the lifetime of the aligned_storage object. So, implementations of Boost.Optional and Boost.Variant are illegal then (?). But it's been like that since C++03 and Boost worked fine all that time, so it looks like this UB existed only "on paper". But C++17 then added "Note: If these conditions are not met, a pointer to the new object can be obtained from a pointer that represents the address of its storage by calling std::launder". So now the language has the ability to deal with that UB, and a question arises, is it possible that compilers could start to use the UB to perform additional optimizations and make it a real UB? Also, I've seen a couple of times on stackoverflow.com people saying that it's actually fine to reinterpret_cast the storage in C++14, but in C++17 it's not (they didn't explain why though). So, can switching from -std=c++14 to -std=c++17 be a breaking change when using Boost? The fact that Boost.Variant and Boost.Optional don't use std::launder - is it an oversight or a conscious decision? Thanks!

2 1

Does boost have something like small_function (with customizable buffer size)?
by Ivan Matek 16 Feb '22

16 Feb '22

I tried googling, but I found nothing. I presume that that means it does not exist, but it is possible it is maybe hidden under some name I could not think of. I am ok with using internal header of some library in case it is code that is covered by tests. regards, Ivan

2 2

MSVC Hint File for Boost.Test macros?
by Dominique Devienne 16 Feb '22

16 Feb '22

Hi. I've just noticed for the first time MSVC (2019 in my case) "squiggles" in my Boost.Test-using unit-test sources, which pointed me to https://docs.microsoft.com/en-us/cpp/build/reference/hint-files?view=msvc-1… and I wonder if anyone has already defined a "Hint File" for Boost.Test, to improve the Navigation Bar experience in Boost.Test-using sources? A quick search didn't turn up anything. Thanks, --DD

1 0