- Boost-users - lists.boost.org

Problem with named_mutex on Windows
by David C. Partridge 13 Nov '23

13 Nov '23

I have a user reporting that the following code in my application's main() hangs unless he uses "Run as Adminstrator": ZTRACE_RUNTIME("Checking Mutex"); bip::named_mutex dssMutex{ bip::open_or_create, "DeepSkyStacker.Mutex.UniqueID.12354687" }; bip::scoped_lock<bip::named_mutex> lk(dssMutex, bip::defer_lock); const bool firstInstance{ lk.try_lock() }; ZTRACE_RUNTIME(" firstInstance: %s", firstInstance ? "true" : "false"); The trace shows "Checking mutex" and then it all stops. Is my code in error and if so what do I need to change? If not, how can I determine what the problem is? On a related issue: I think that this is C++ Exception safe, as the mutex will be unlocked and deleted. However, if a C exception occurs then how should I clean up? Is the named_mutex persistent over reboots? If so, where is it held (in case I need to do a manual cleanup). Many thanks David

1 0

Optimizing serialization of std containers
by Gidi Gal 05 Nov '23

05 Nov '23

Hello, Are there any settings or additional code required to optimize the serialization of std containers ? I serialize a nested container: std::vector<std::deque<int>>. The max size of each deque entry is 20. I include boost/serialization/deque.hpp and boost/serialization/vector.hpp and I serialize the container in the following way: std::ofstream ofs(outFileName); boost::archive::binary_oarchive oa(ofs); oa << data; I created data with 10600 integers in the deque. The size of the serialized output file is 54493. Now, I test an alternate serialization. I serialized the size of the vector and then per each entry I serialize its size, which cannot be more than 20, so char is enough for that, next I serialize the integers in this entry. The size of the serialized output file is 43484. Is there a way to achieve better results for the default serialization ? Thanks, Gidi

1 0

why diagnostic_information is std::exception::what: Unknown exception
by Bernard 29 Oct '23

29 Oct '23

greetings kind regards may i please inquire how not to obtain "std::exception::what: Unknown exception" from diagnosic_inforumation() . my meaning is to inquire how to obtain as per example on boost web page https://www.boost.org/doc/libs/1_83_0/libs/exception/doc/tutorial_diagnosti… output : "std::exception::what: example_io error" id est where did "example_io error" come from as neither boost::exception nor std:::exception accept constructor string arguments . please my code below . thank you kindly #include "stl" // #includes all stl #include files #include "boost\exception\all.hpp" using namespace std; struct ceXception : virtual boost::exception, virtual std::exception { using this_type = ceXception; ceXception() {} auto what() { cerr << __FUNCSIG__ << endl; return string("return from " + string(__FUNCSIG__)); } template<typename charType> friend std::basic_ostream<charType>& operator<<(std::basic_ostream<charType>& _ostream, const this_type&) { cerr << "to cerr from " << __FUNCSIG__ << endl; _ostream << "to ostream from " << __FUNCSIG__ << endl; return _ostream; } }; void foo() { try { BOOST_THROW_EXCEPTION(ceXception()); } catch (ceXception& e) { cerr << boost::diagnostic_information(e); } } int main() { foo(); return 0; }

2 2

Async review scheduled for September 22, 2023 - October 2, 2023
by Mateusz Loskot 07 Sep '23

07 Sep '23

Hi, Following request from Nial and Klemens, we have scheduled new round of the Async review for September 22, 2023 - October 2, 2023 https://www.boost.org/community/review_schedule.html Best regards, -- Mateusz Loskot, on behalf of the Review Wizards

1 0

Error LNK1104 cannot open file 'boost_unit_test_framework-vc143-mt-x64-1_82.lib' cal_data_gain_pwr_test C:\Users\mushtaq.syed\Downloads\uhd-master\host\build\tests\LINK 1
by Mushtaq A. Syed, Ph.D. 28 Aug '23

28 Aug '23

Hi: My project uses the Boost library. I have installed C:\Program Files\Boost\boost_1_82_0. I also built using the bootstrap and .\b2 commands from the command window. This was because all the libboost libraries in C:\Program Files\Boost\boost_1_82_0\stage\lib were missing. Now when I build my code using Visual Studio 2022, I am getting the above error. I searched my Boost root folder and cannot find boost_unit_test_framework-vc143-mt-x64-1_82.lib; however, I do see libboost_unit_test_framework-vc143-mt-x64-1_82.lib and other libboost libraries but not a single boost library. I don’t know why it is looking for boost_unit_test_framework-vc143-mt-x64-1_82.lib and not libboost_unit_test_framework-vc143-mt-x64-1_82.lib. Could you please help resolve this? Thanks a lot! Cheers, Mushtaq ---------------------------- Mushtaq Syed, Ph.D. Principal Digital Signal Processing Engineer Verus Research [cid:image5fd716.JPG@ebfac5a4.47a0da54]<http://> Direct 505-396-7109 Cell 408-514-7821 6100 Uptown Blvd NE, Suite 260 Albuquerque, New Mexico 87110 verusresearch.net ---------------------------- NOTICE: This electronic mail message is intended exclusively for the individual or entity to which it is addressed. This message, together with any attachment, may contain sensitive or privileged information. Any unauthorized review, use, printing, retention, copying, disclosure, or distribution of said email is strictly prohibited. If you have received this message in error, please (1) immediately advise the sender by reply email message and (2) delete all copies of this message

2 3

Quadmath.h not found for float128 arm64 rocky linux
by David Frank 25 Aug '23

25 Aug '23

When compile with boost float128 on arm64 rocky linux, i got a failure of missing quadmath.h Thanks.

3 2

[Compiler] Boost compatibility in a untested compiler version
by Kankanamge, Gimhani 17 Aug '23

17 Aug '23

Hi team, Based on release notes for boost 1.83.0, there is a list of tested compilers (https://www.boost.org/users/history/version_1_83_0.html) But, we are going to use boost 1.83.0 in a different compiler which is not listed here(GCC 8.5.0). In such a case, what is the approach we should use to verify that boost is compatible in our given platform? Thank you. Gimhani Uthpala ------------------------------------------------------------------------------------------------------------ Please read these warnings and restrictions: This e-mail transmission is strictly confidential and intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or CONFIDENTIAL information. The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited and could, in certain circumstances, constitute a criminal offence. If you have received this e-mail in error or are not an intended recipient please inform London Stock Exchange Group (“LSEG”) immediately by return e-mail or telephone 020 7797 1000. LSEG may collect, process and retain your personal information for its business purposes. For more information please see our Privacy Policy. We advise that in keeping with good computing practice the recipient of this e-mail should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this e-mail. E-mail may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof. Calls to London Stock Exchange Group may be recorded to enable LSEG to carry out its regulatory responsibilities. For more details on the LSEG group of companies click here London Stock Exchange Group plc 10 Paternoster Square London EC4M 7LS Registered in England and Wales No 05369106 ------------------------------------------------------------------------------------------------------------

2 1

JSON and no-alloc
by Marc Oscar Singer 14 Aug '23

14 Aug '23

Greetings, I'm targeting the boost JSON library for an embedded target. There appears to be one place where there could be either a beneficial new feature, or the feature exists and I'm not seeing it. The section about Avoiding Dynamic Allocation is close to what we'd like to see, except that we don't want to depend on a stack buffer for value data. All of the text of the JSON message is present in the string view. It would be desirable to reference the values from there. Let me be a little more explicit. We receive a message in JSON format. The whole of this message must be received before we can pass it to the JSON parser. It's /possible/ to let the JSON parser manage the message as it arrives and manage both the parse and storage of the content. Doing so would require shifting some responsibilities within the firmware that are difficult to change. We parse out the fields we care about and then want to hold onto these values for some time without retaining the memory necessary for the parse itself. Since all of the values and keys are present in the original source buffer passed to parse() as a string_view, we could simply save the string_views for the values and discard the JSON parser. Except, this parser copies the value to another buffer s.t. discarding the parser invalidates the value string_views. Alternatively, if the values themselves were returned as string_views into the source buffer, these string_views would (could) survive destruction of the parser. If we are missing the method by which this can be implemented with the current parser, we'd be delighted to hear it. Cheers -- /Marc Oscar Singer/ *Woollysoft* +1.206.328.1718

3 4

Abwesenheitsnachricht: JSON and no-alloc
by Sören Textor 14 Aug '23

14 Aug '23

Derzeit bin ich nicht im Hause Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen bitte support(a)ditec-gmbh.de oder Telefonhotline +49-6221-31698-110 oder die Zentrale +49-6221-31698-0 kontaktieren. Mit freundlichen Grüßen Dr. Sören Textor ----------------------------------------------- DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights.

1 0

Full-Text Search is LIVE!
by Vinnie Falco 10 Jul '23

10 Jul '23

Greetings. I am proud to announce that Mohammad’s excellent work on implementing a full-text search which looks into all the Boost libraries and their documentation is now complete, and has been published to the live website. You can access the search by pressing the Search button in the top right of the page: https://boost.org Please note that this is only the first iteration of this search tool and as such it will probably not give the perfect results that everyone expects every time. But now that we have something in place we can feedback, brainstorm on how to make it better, and iterate on it so that it evolves into something that consistently enhances the Boost user experience. To report problems or suggestions related to the search including the user interface, and the indexed contents, please open an issue in the Boost website repository: https://github.com/boostorg/website/issues There is also a “Report Issue” button in the search UI. Thanks!

1 0