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

Boost::Interprocess mutex with condition variable
by Riskybiz 17 Jul '13

17 Jul '13

I'm trying to get a working implementation of a boost::interprocess named_mutex with a named_condition_variable. I have created the following toy console applications to try and understand what's necessary. The console application 'Sleeper' is run first; it simply creates some resources and then goes to sleep. Then 'Waker' is run with the intention that it would cause the 'Sleeper' instance to resume execution and print out a further message. Ultimately the intention is to have one Waker process and several Sleeper processes. When each application is run in a separate terminal window then the Sleeper process sleeps and the Waker process tries to wake; but it is ineffective. Can anyone advise what is wrong here and how to get the notify_all() to take effect? Thanks Riskybiz. // Sleeper.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Clean up resources from any prior instances named_condition::remove("msm_named_condition"); named_mutex::remove("msm_named_mutex"); //shared_memory_object::remove("msm"); //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(create_only, "msm", 10000); named_mutex *nm = new named_mutex(create_only, "msm_named_mutex"); named_condition *nc = new named_condition(create_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to sleep now...." << std::endl; nc->wait(lock);//induce wait std::cout << "Wide awake and back in the room" << std::endl;//print this out on waking up } catch(interprocess_exception &ipe) { std::cout << "Error in Sleeper process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; } // Waker.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(open_only, "msm"); named_mutex *nm = new named_mutex(open_only, "msm_named_mutex"); named_condition *nc = new named_condition(open_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to Notify...." << std::endl; nc->notify_all();//notify to release the wait condition std::cout << "Wakey Wakey....Notified...." << std::endl; } catch(interprocess_exception &ipe) { std::cout << "Error in Waker process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; }

2 1

multi_index_container with protected constructor
by Horváth Imre 17 Jul '13

17 Jul '13

Hi, I want to use boost::multi_index_container with a class that have protected constructors, but the compile fails. I think I should make multi_index_container a friend of my class, but I don't know how. #include <iostream> #include <boost/shared_ptr.hpp> #include <boost/multi_index_container.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/composite_key.hpp> #include <boost/multi_index/mem_fun.hpp> class Item { public: typedef boost::shared_ptr<Item> P; static P create() { return P(new Item()); } static P create(P item) { return P(new Item(item)); } protected: Item() { } Item(P item) : source(item->get_source()) , target(item->get_target()) { } public: std::string source; std::string target; std::string get_source() const {return source;} std::string get_target() const {return target;} struct key : boost::multi_index::composite_key< P, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_source>, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_target> >{}; typedef boost::multi_index_container< P, boost::multi_index::indexed_by< boost::multi_index::ordered_non_unique< key, boost::multi_index::composite_key_result_less<key::result_type> > > > index_t; }; int main() { Item::index_t index; Item::P t1 = Item::create(); index.insert(t1); return 0; } Thanks in advance: Imre Horvath

2 2

[Boost.Log] Example tutorial_fmt_stream.cpp does not compile
by Mario Knezović 17 Jul '13

17 Jul '13

I am trying to change date formatting exactly in the way as described in the tutorial, sub-section "Specialized formatters": http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/tutorial/formatt… What I want to achieve is pretty simple, change month output from the default "Abbreviated month name" (%b): [2013-Jul-08 10:51:00.989235] to "Month name as a decimal 01 to 12" (%m): [2013-07-08 10:51:00.989235] Unfortunately this does not compile, nor does the example from which the snipped is taken: "tutorial_fmt_stream.cpp". The interesting part in the example source is commented out by default. (But this was the case with other examples too.) The part I'm interested in is in line 60 (from current Boost 1.54.0): expr::format_date_time< boost::posix_time::ptime >("TimeStamp", "%Y-%m-%d %H:%M:%S") The errors I get (Win7, 64-bit, MS VC++ 2010): error C2027: use of undefined type "boost::log::v2s_mt_nt5::expressions::aux::date_time_formatter_generator_traits<T,CharT>" d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 error C3861: "parse": Identifier not found. d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 I hope somebody can help or point me in the right direction. Thank you! Mario Knezović

1 1

[log, spirit] phoenix version conflict
by Yi Ding 17 Jul '13

17 Jul '13

It looks like Boost.Log conflicts with Boost.Spirit because they're using different version of Boost Phoenix? Take this example file: #include <boost/log/common.hpp> #include <boost/log/sinks.hpp> #include <boost/spirit/include/karma.hpp> int main() { } We get this warning: In file included from /opt/boost_1_54_0/include/boost/log/detail/custom_terminal_spec.hpp:21, /opt/boost_1_54_0/include/boost/spirit/include/phoenix_core.hpp:13:1: warning: "BOOST_PHOENIX_DEFINE_CUSTOM_TERMINAL" redefined /opt/boost_1_54_0/include/boost/phoenix/core/terminal.hpp:22:1: warning: this is the location of the previous definition There are a bunch of errors that result as well.

2 2

How to build libboost_filesystem-vc110-mt-sgd-1_54.lib with VS2012 x64?
by Amann, Julian 17 Jul '13

17 Jul '13

I have some trouble building the boost filesystem lib using VS2012 x64. I use the following instructions to build it: 1. Download boost 1.54.0 from http://www.boost.org/ 2. Extract files (e.g. "C:\thirdparty\vs2013\x64\boost_1_54_0") 3. Start Visual Studio 2012 x64 command prompt 4. Change to boost directory (e.g. "cd C:\thirdparty\vs2010\x64\boost_1_54_0") 5. Execute .\bootstrap.bat 6. Execute b2 address-model=64 toolset=msvc-11.0 --build-type=complete stage --with-filesystem --with-signals --with-system Unfortunately the file "libboost_filesystem-vc110-mt-sgd-1_54.lib" is not build Previously I used boost 1.51.0, 1.52.0 and 1.53.0. In this releases the libboost_filesystem-vc110-mt-sgd-1_5x.lib was always build without any problems. Did anybody mange to build this lib using VS2012? Which instructions do you use to build it? Best regards, Julian

1 0

[log] operator<< best practices
by Yi Ding 16 Jul '13

16 Jul '13

I noticed boost log has a helper function for operator<< template< typename CharT, typename TraitsT, typename AllocatorT, typename T > inline basic_formatting_ostream< CharT, TraitsT, AllocatorT >& operator<< (basic_formatting_ostream< CharT, TraitsT, AllocatorT >& strm, T const& value) { strm.stream() << value; return strm; } which is useful because a lot of code has operator<< overloads specifically for std::ostream. Recently we've moved our code to use a generic template <class stream, int N> inline stream& operator<<(stream& os, const BlahClass& value) which conflicts with the boost log helper function, but is useful for our own ostream-like classes. What's the best practice here? Can we make the two mesh by using traits of some sort? Should we do all of our type to string conversions ahead of time using something like folly::to? Cheers, Yi

1 0

[Boost.Log] An update on severity level issue
by Leo Carreon 16 Jul '13

16 Jul '13

Hi all, I am still having the issue with the missing severity level string in the logs and have decided to give you my latest code. Here is my current code: #include <iostream> #include <iomanip> #include <cstdlib> #include <fstream> #include <boost/log/core.hpp> #include <boost/log/sources/global_logger_storage.hpp> #include <boost/log/sources/severity_logger.hpp> #include <boost/log/sources/record_ostream.hpp> #include <boost/log/attributes/clock.hpp> #include <boost/log/attributes/current_process_name.hpp> #include <boost/log/attributes/current_process_id.hpp> #include <boost/log/attributes/current_thread_id.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/from_stream.hpp> #include <boost/log/utility/manipulators/to_log.hpp> #include <boost/log/utility/formatting_ostream.hpp> using namespace std; namespace logging = boost::log; namespace keywords = boost::log::keywords; namespace expr = boost::log::expressions; namespace attr = boost::log::attributes; namespace src = boost::log::sources; #define LFC1_LOG_TRACE(logger) BOOST_LOG_SEV(logger, trace) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_DEBUG(logger) BOOST_LOG_SEV(logger, debug) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_INFO(logger) BOOST_LOG_SEV(logger, info) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_WARNING(logger) BOOST_LOG_SEV(logger, warning) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_ERROR(logger) BOOST_LOG_SEV(logger, error) << "(" << __FILE__ << ", " << __LINE__ << ") " static const auto RET_SUCCESS = 0; static const auto RET_FAIL = 1; static const auto LOGGING_ENVIRONMENT_NAME = "LOGGING_CONFIG_FILE_NAME"; static const auto DEFAULT_LOGGING_CONFIG_FILE_NAME = "config/LogSettings.txt"; enum ESeverityLevel { trace, debug, info, warning, error }; BOOST_LOG_ATTRIBUTE_KEYWORD(severity, "Severity", ESeverityLevel) ostream& operator<<(ostream& arStream, ESeverityLevel avLevel) { static const char* pStrings[] = { "trace", "debug", "info", "warning", "error" }; if (static_cast<size_t>(avLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[avLevel]; } else { arStream << static_cast<int>(avLevel); } return arStream; } logging::formatting_ostream& operator<< ( logging::formatting_ostream& arStream, logging::to_log_manip<ESeverityLevel, tag::severity> const& arManip ) { static const char* pStrings[] = { "TRACE", "DEBUG", "INFO", "WARNING", "ERROR" }; ESeverityLevel vLevel = arManip.get(); if (static_cast<size_t>(vLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[vLevel]; } else { arStream << static_cast<int>(vLevel); } return arStream; } BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(SLogger, src::severity_logger<ESeverityLevel>) static void gvLoggingInit(const char* apConfigFileName = nullptr) { // Obtain the name of the logging configuration file. if (apConfigFileName == nullptr || apConfigFileName[0] == 0) { if ((apConfigFileName = getenv(LOGGING_ENVIRONMENT_NAME)) == 0 || apConfigFileName[0] == 0) { apConfigFileName = DEFAULT_LOGGING_CONFIG_FILE_NAME; } } // Open the logging configuration file. ifstream vConfigFile(apConfigFileName); if (!vConfigFile.is_open()) { // TODO: throw an exception } // Read the contents of the logging configuration file. logging::init_from_stream(vConfigFile); // Add the logging attributes that we require. auto pCore = logging::core::get(); pCore->add_global_attribute("TimeStamp", attr::local_clock()); pCore->add_global_attribute("Process", attr::current_process_name()); pCore->add_global_attribute("ProcessID", attr::current_process_id()); pCore->add_global_attribute("ThreadID", attr::current_thread_id()); pCore->set_filter(severity >= info); } int main() { auto vRetVal = RET_SUCCESS; try { gvLoggingInit(); auto& vLogger = SLogger::get(); LFC1_LOG_TRACE(vLogger) << "A trace severity message"; LFC1_LOG_DEBUG(vLogger) << "A debug severity message"; LFC1_LOG_INFO(vLogger) << "An informational severity message"; LFC1_LOG_WARNING(vLogger) << "A warning severity message"; LFC1_LOG_ERROR(vLogger) << "An error severity message"; } catch (exception& crException) { cerr << crException.what() << endl; vRetVal = RET_FAIL; } catch (...) { cerr << "Unknown exception" << endl; vRetVal = RET_FAIL; } return vRetVal; } Here is what’s in the settings file: [Core] Filter="%Severity% >= 2" DisableLogging=false [Sinks.File] Destination=TextFile FileName=log/test_logging_%N.log RotationSize=1048576 Target=logs MaxSize=10485760 ScanForFiles=All Format="%TimeStamp% [%Severity%] %Process%:%ProcessID%:%ThreadID% %Message%" As mentioned in a previous post, the issue I’m having is this is how the resulting log records look like: 2013-Jul-16 11:24:59.758177 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 240) An informational severity message 2013-Jul-16 11:24:59.758812 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 241) A warning severity message 2013-Jul-16 11:24:59.758851 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 242) An error severity message Note that the severity string is missing from the above log records. Does anyone know I can fix the code to make the severity string show up in the log records? Another question I have is how do I change the format of the date in the timestamp from YYY-MMM-DD to YYYY-MM-DD. I am sticking to using logging settings from a file because I want an application user to be able to control where log records go. However, I am open to the idea of setting the format within the code but at the moment there is no option of setting the format when a settings file is used. It would be nice to have a function within the logging core which allows us to obtain a pointer/reference to the existing sinks. Kind regards, Leo

1 0

Problems include the RANDOM LIBRARIES, in a console project, in Windows.
by Alberto Aliberti 16 Jul '13

16 Jul '13

I used the Random libraries of Boost collection. I have implemented it in my program. A program for the chess analysis . Now, at compile time I have no problem. Everything ok, the console project is compiled without errors. During run time, the functions of Boost Random libraries, correctly generate a random number. But after a few repetitions of the loop (from 2/3 to a few tens of loops), the program crashes. The strange thing that the crash does not occur in the functions where I use the random functions, but occurs in the chess engine that does not use these functions, and thus in theory should not be influenced by it. But if I do not use the functions of Boost library and use the basic function of C + + (rand ();) I have no problems. I work in Windows. My project is a console project compiled with VC + +2010. Also I have wrote a test program with VC + +2010, which generates a sequence of random numbers, using Boost libraries. In this case I have no problems. Only when I implement the libraries in the chess program I have problems. So it seems that your libraries are in conflict with the chess engine. What do you recommend for the search for the cause of the problem? The headers and the function use by me in my program: #include <boost/random/mersenne_twister.hpp> #include <boost/random/uniform_smallint.hpp> // initializes boost random generator seed boost::random::mt19937 gen; // random function int ransel(int minr,int maxr) { boost::random::uniform_smallint <> dist(minr, maxr); return dist(gen); } ________ Then I call the ransel() function in the loop of my program to select the chess moves.

2 2

quick threading query
by Sean Farrow 15 Jul '13

15 Jul '13

Hi all, I have a quick threading query. I'm in the process of rewriting an application to take advantage of concurrency. This application is cross-platform so I'm looking at the boost threading library to solve the issue. When the window is created I'm creating a thread, then when the user chooses to quit I need to notify the created thread to stop running. Would a future do the job, if this is the case where should this be stored in the class that represents the window or in the class that represents the thread, I'm really not wanting to store this globally. Any help appreciated. Cheers Sean.

2 1

1.54.0 breaks bcp-produced partial builds?
by Bruce Stephens 15 Jul '13

15 Jul '13

Back in 1.53.0, I could do the following: ./bootstrap.sh (cd tools/bcp; ../../b2) bin.v2/.../bcp build filesystem .../temp Then in .../temp run ./bootstrap.sh and ./b2 to build just filesystem (or whatever else I copied). In 1.54.0, the copy doesn't build: brs% ./b2 Building the Boost C++ Libraries. /auto/tmpfs/temp/tools/build/v2/build/targets.jam:397: in find-really *** argument error * rule project.is-registered-id ( id ) * called with: ( ) * missing argument id /auto/tmpfs/temp/tools/build/v2/build/project.jam:600:see definition of rule 'project.is-registered-id' being called /auto/tmpfs/temp/tools/build/v2/build/targets.jam:457: in class(a)project-target.find /auto/tmpfs/temp/tools/build/v2/build/targets.jam:841: in resolve-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build-system.jam:707: in load /auto/tmpfs/temp/tools/build/v2/kernel/modules.jam:289: in import /auto/tmpfs/temp/tools/build/v2/kernel/bootstrap.jam:139: in boost-build /auto/tmpfs/temp/boost-build.jam:17: in module scope

1 1