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

[Log] Extract severity value
by Olivier Tournaire 17 Jul '14

17 Jul '14

Hi all, I am trying to extract severity level from a log record, but i seems that I am doing it the wrong way. Here is the code I use: void LogDockWidget::receiveLog(boost::log::record_view const& rec, const std::string& log) { logging::value_ref< logging::trivial::severity_level > level = logging::extract< logging::trivial::severity_level >("Severity", rec); // ... } Here level.get() always returns "info". All my logs are done with the BOOST_LOG_TRIVIAL(...) macro. The formatter whereas displays correctly the severity level. Here is how it is defined: void LogDockWidget::init_logging() { boost::shared_ptr< logging::core > core = logging::core::get(); typedef sinks::synchronous_sink< QTextEditFormattedSinkBackend > sink_t; boost::shared_ptr< sink_t > sink(new sink_t); // ... logging::add_file_log( keywords::file_name = logFilename, keywords::auto_flush = true, keywords::format = ( BUILD_LOG_FORMATTER() ) ); sink->set_formatter( BUILD_LOG_FORMATTER() ); core->add_sink(sink); // Add attributes that we will use logging::add_common_attributes(); core->add_global_attribute( "ThreadID", attrs::current_thread_id()); } #define BUILD_LOG_FORMATTER() \ expr::stream \ << "[" << expr::format_date_time< boost::posix_time::ptime >("TimeStamp", "%Y-%m-%d %H:%M:%S") << "] " \ << expr::attr<unsigned int>("LineID") << " " \ << ": <" << logging::trivial::severity << "> " \ << " [" << expr::attr<attrs::current_thread_id::value_type>("ThreadID") << "] " \ << expr::if_(expr::has_attr(scope_attribute)) \ [ \ expr::stream << "[" << scope_attribute << "] " \ ] \ << expr::message Could you please let me know what I am doing wrong? Regards, Olivier

2 2

Re: [Boost-users] Intrusive: Checking for undefined behaviour
by Brian Wood 16 Jul '14

16 Jul '14

Ion Gazta?aga writes: >El 15/07/2014 5:33, Brian Wood escribi?: >> I was reading here about some of the sanitizers >> >> http://cplusplusmusings.wordpress.com/ >> >> and decided to try it out the undefined behavior >> sanitizer on some code. One thing that came >> out was related to the Intrusive library. > > Can you try with the release candidate (http://boost.cowic.de/rc/) for > Boost 1.56? I solved some undefined behaviour issues recently but I > don't know if this is one of them. I tested it with 1.56 now and the sanitizer is no longer reporting a problem with Intrusive. It looks like whatever you did has helped. I appreciate your being on top of this. -- Brian Ebenezer Enterprises - "Let a man so consider us, as servants of Messiah and stewards of the mysteries of G-d." First Corinthians 4 http://webEbenezer.net

2 1

1.56.0 beta release candidate 2 available for testing
by Marshall Clow 16 Jul '14

16 Jul '14

The second release candidate files for 1.56.0 beta are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost-1_56_0_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5 Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively. Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim(a)gmail.com was seeing have been fixed. I would like to post this to SourceForge Thursday night/Friday morning, if possible. Thank you. --The release managers

9 12

[log] translating 3rd party logging messages
by Olaf Peter 16 Jul '14

16 Jul '14

Hello, shown my translator for Qt using boost.log: void qt_message_translator(QtMsgType type, const QMessageLogContext &context, const QString &msg) { QString const context_message = QString("Qt [") + context.function + " (" + context.file + ":" + QString::number(context.line) + ")] "; QByteArray const ctx_msg = context_message.toUtf8(); QByteArray const qt_msg = msg.toUtf8(); boost::log::sources::severity_logger<severity_level> slg; switch (type) { case QtDebugMsg: BOOST_LOG_SEV(slg, debug) << ctx_msg.constData() << qt_msg.constData(); break; case QtWarningMsg: BOOST_LOG_SEV(slg, warning) << ctx_msg.constData() << qt_msg.constData(); break; case QtCriticalMsg: BOOST_LOG_SEV(slg, error) << ctx_msg.constData() << qt_msg.constData(); break; case QtFatalMsg: BOOST_LOG_SEV(slg, fatal) << ctx_msg.constData() << qt_msg.constData(); break; default: BOOST_LOG_SEV(slg, fatal) << ctx_msg.constData() << qt_msg.constData(); break; } } ... qInstallMessageHandler(qt_message_translator); The problem is more of cosmetic nature; the logging format output is different from what is used normally - it looks alien. Since the context data is available I assume I can write an own logging source writing/fill the log records filled with the context information. Additionally I want to add a "Scope" or "Library" flag "Qt" (Scope may be not the best choise since it's used in another context). But I didn't find an example in the boost.log module to find the entry; is writing an own source the right way? How to use it in the qt_message_translator? Thanks, Olaf

1 2

adjacency_list.hpp won't compile
by Alexander While 16 Jul '14

16 Jul '14

Hello, I just recently found Boost, and I am attempting to use it in a project I am working on. However, in my attempts to make simple graphs with the graph/adjacency_list.hpp subdirectory, I get a compiler error within the code for adjacency_list.hpp. I don't know if I can copy the error message correctly, but the errors seem centered around lines 1503-1505, those saying typedef typename lookup_one_property<vertex_property_type, vertex_bundle_t>::type vertex_bundled; typedef typename lookup_one_property<edge_property_type, edge_bundle_t>::type edge_bundled; typedef typename lookup_one_property<graph_property_type, graph_bundle_t>::type graph_bundled; then lines 2027 and 275 are mentioned. The code I myself wrote compiles fine on its own. I'm using the IDE Dev-C++.

2 1

Intrusive: Checking for undefined behaviour
by Brian Wood 15 Jul '14

15 Jul '14

I was reading here about some of the sanitizers http://cplusplusmusings.wordpress.com/ and decided to try it out the undefined behavior sanitizer on some code. One thing that came out was related to the Intrusive library. /home/brian/boost_1_55_0/boost/intrusive/detail/tree_node.hpp:164:44: runtime error: member access within null pointer of type 'const boost::intrusive::bhtraits<myString, boost::intrusive::rbtree_node_traits<void *, false>, 2, boost::intrusive::default_tag, 3>' I have a couple of lines that may be related to: struct myString : set_base_hook<::boost::intrusive::link_mode<::boost::intrusive::auto_unlink> > and ::boost::intrusive::set<myString, constant_time_size<false> > files; Can someone tell me how serious this is? Thank you. -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 1

Re: [Boost-users] [coroutine] Is there a max number of coroutines that can be created?
by José 15 Jul '14

15 Jul '14

1 0

[Boost Log] how to print source code file name and line number in boost log
by Pritesh Acharya 15 Jul '14

15 Jul '14

Boost version: 1.55.0 OS: Windows 8 IDE: Visual Studio 2010 Boost Module: Boost Log I'm using Boost Logging in my C++ application. I have been able to generate log of this format [2014-Jul-15 10:47:26.137959]: <debug> A regular message I want to be able to add source file name and line number where the log is generated, But i'm not able to do so. [2014-Jul-15 10:47:26.137959]: <debug> [filename:line_no] A regular message example: [2014-Jul-15 10:47:26.137959]: <debug> [helloworld.cpp : 12] A regular message Source Code: #include <boost/log/core.hpp>#include <boost/log/trivial.hpp>#include <boost/log/expressions.hpp>#include <boost/log/sinks/text_file_backend.hpp>#include <boost/log/utility/setup/file.hpp>#include <boost/log/utility/setup/common_attributes.hpp>#include <boost/log/sources/severity_logger.hpp>#include <boost/log/sources/record_ostream.hpp>#include <boost/log/expressions.hpp>#include <boost/log/support/date_time.hpp>#include <boost/log/attributes/attribute.hpp>#include <boost/log/attributes/attribute_cast.hpp>#include <boost/log/attributes/attribute_value.hpp>#include <boost/make_shared.hpp>#include <boost/property_tree/ptree.hpp> namespace logging = boost::log;namespace src = boost::log::sources;namespace sinks = boost::log::sinks;namespace keywords = boost::log::keywords; void init(){ logging::add_file_log ( keywords::file_name = "sample_%N.log", /*< file name pattern >*/ keywords::rotation_size = 10*1024*1204, /*< rotate files every 10 MiB... >*/ keywords::time_based_rotation = sinks::file::rotation_at_time_point(0, 0, 0), /*< ...or at midnight >*/ keywords::format = ( boost::log::expressions::stream << boost::log::expressions::format_date_time< boost::posix_time::ptime >("TimeStamp", "%Y-%m-%d_%H:%M:%S.%f") << ": <" << boost::log::trivial::severity << "> " << boost::log::expressions::smessage ) );} int main(int, char*[]){ init(); logging::add_common_attributes(); using namespace logging::trivial; src::severity_logger< severity_level > lg; BOOST_LOG_SEV(lg, debug) << "A regular message"; return 0;}

1 0

TCP resolver creates TppWorkerThreads on windows only
by Chris Stankevitz 14 Jul '14

14 Jul '14

Hello, When I run the following code on windows, some threads are created, presumably by winsock. These threads are "named" _TppWorkerThread. This does not happen on linux. These threads do not stop when all the boost objects go out of scope, but I wish they did. Q1: Am I doing something wrong? Q2: Is there a boost way for me to stop these threads? Thank you, Chris int main() { { boost::asio::io_service DummyIoService; boost::asio::ip::tcp::resolver Resolver(DummyIoService); Resolver.resolve( boost::asio::ip::tcp::resolver::query("localhost", "3000")); } // At this point, there are three extra threads running: // // _TppWorkerThread@4 _ZwWaitForWorkViaWorkerFactory@8 // _TppWorkerThread@4 _ZwWaitForWorkViaWorkerFactory@8 // _TppWaiterpThread@4 _ZwWaitForMultipleObjects@20 return 0; }

2 2

[test] Bluegene/Q issue: sigaltstack
by Ewart Timothée 14 Jul '14

14 Jul '14

Dear All, I already posted on the boost.test user mailing list, but as my question was to technical they forward me their ( http://lists.boost.org/boost-testing/2014/07/7692.php ) I installed/compiled boost on the BG/Q (with gcc provided by IBM) but I am confronted to a issue, the framework crashed (compute node) due to a call to the system function sigaltstack. >From my previous post, a boost user suggests me to disable a macro into execution_monitor.ipp line 176 https://github.com/boostorg/test/blob/boost-1.55.0/include/boost/test/impl/… If I disable this macro the framework works well. Into Boost, this macro is defined between a !defined # if !defined(__CYGWIN__) && !defined(__QNXNTO__) # define BOOST_TEST_USE_ALT_STACK # endif Should we add a C++ macro provided by the compiled to disable this define ? I give a list of the macro of GCC for the BG/Q #define __DBL_MIN_EXP__ (-1021) #define __FLT_MIN__ 1.17549435e-38F #define __CHAR_BIT__ 8 #define _ARCH_PPCGR 1 #define __PPC64__ 1 #define __WCHAR_MAX__ 2147483647 #define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_1 1 #define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_2 1 #define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 1 #define __DBL_DENORM_MIN__ 4.9406564584124654e-324 #define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_8 1 #define __FLT_EVAL_METHOD__ 0 #define __unix__ 1 #define __DBL_MIN_10_EXP__ (-307) #define __FINITE_MATH_ONLY__ 0 #define __GNUC_PATCHLEVEL__ 6 #define __DEC64_MAX_EXP__ 385 #define __SHRT_MAX__ 32767 #define __LDBL_MAX__ 1.79769313486231580793728971405301e+308L #define _ARCH_PPC 1 #define __UINTMAX_TYPE__ long unsigned int #define __linux 1 #define __DEC32_EPSILON__ 1E-6DF #define __CHAR_UNSIGNED__ 1 #define __LDBL_MAX_EXP__ 1024 #define __linux__ 1 #define __SCHAR_MAX__ 127 #define __DBL_DIG__ 15 #define __SIZEOF_INT__ 4 #define __SIZEOF_POINTER__ 8 #define __USER_LABEL_PREFIX__ #define __STDC_HOSTED__ 1 #define __LDBL_HAS_INFINITY__ 1 #define __FLT_EPSILON__ 1.19209290e-7F #define __LDBL_MIN__ 2.00416836000897277799610805135016e-292L #define __DEC32_MAX__ 9.999999E96DF #define __SIZEOF_LONG__ 8 #define __DECIMAL_DIG__ 33 #define __gnu_linux__ 1 #define __LDBL_HAS_QUIET_NAN__ 1 #define __GNUC__ 4 #define __FLT_HAS_DENORM__ 1 #define __SIZEOF_LONG_DOUBLE__ 16 #define __BIGGEST_ALIGNMENT__ 16 #define __DBL_MAX__ 1.7976931348623157e+308 #define __DBL_HAS_INFINITY__ 1 #define __DEC32_MIN_EXP__ (-94) #define __LDBL_HAS_DENORM__ 1 #define __DEC128_MAX__ 9.999999999999999999999999999999999E6144DL #define __DEC32_MIN__ 1E-95DF #define __DBL_MAX_EXP__ 1024 #define __DEC128_EPSILON__ 1E-33DL #define __LONG_LONG_MAX__ 9223372036854775807LL #define __SIZEOF_SIZE_T__ 8 #define __PPC__ 1 #define __SIZEOF_WINT_T__ 4 #define __bg__ 1 #define __GXX_ABI_VERSION 1002 #define __FLT_MIN_EXP__ (-125) #define __DBL_MIN__ 2.2250738585072014e-308 #define __LONGDOUBLE128 1 #define __LP64__ 1 #define __DEC128_MIN__ 1E-6143DL #define __REGISTER_PREFIX__ #define __DBL_HAS_DENORM__ 1 #define __NO_INLINE__ 1 #define __FLT_MANT_DIG__ 24 #define __VERSION__ "4.4.6" #define __BIG_ENDIAN__ 1 #define __powerpc64__ 1 #define __DEC64_EPSILON__ 1E-15DD #define __DEC128_MIN_EXP__ (-6142) #define __powerpc__ 1 #define unix 1 #define __SIZE_TYPE__ long unsigned int #define __ELF__ 1 #define __FLT_RADIX__ 2 #define __LDBL_EPSILON__ 4.94065645841246544176568792868221e-324L #define __SIZEOF_PTRDIFF_T__ 8 #define __DEC32_SUBNORMAL_MIN__ 0.000001E-95DF #define __FLT_HAS_QUIET_NAN__ 1 #define __FLT_MAX_10_EXP__ 38 #define __LONG_MAX__ 9223372036854775807L #define __DEC128_SUBNORMAL_MIN__ 0.000000000000000000000000000000001E-6143DL #define __FLT_HAS_INFINITY__ 1 #define __unix 1 #define __DEC64_MAX__ 9.999999999999999E384DD #define __CHAR16_TYPE__ short unsigned int #define __DEC64_MANT_DIG__ 16 #define __DEC32_MAX_EXP__ 97 #define _BIG_ENDIAN 1 #define linux 1 #define __LDBL_MANT_DIG__ 106 #define __DBL_HAS_QUIET_NAN__ 1 #define __WCHAR_TYPE__ int #define __SIZEOF_FLOAT__ 4 #define __DEC64_MIN_EXP__ (-382) #define __FLT_DIG__ 6 #define __INT_MAX__ 2147483647 #define __LONG_DOUBLE_128__ 1 #define __FLT_MAX_EXP__ 128 #define __DBL_MANT_DIG__ 53 #define __DEC64_MIN__ 1E-383DD #define __WINT_TYPE__ unsigned int #define __SIZEOF_SHORT__ 2 #define __LDBL_MIN_EXP__ (-968) #define __LDBL_MAX_10_EXP__ 308 #define __DBL_EPSILON__ 2.2204460492503131e-16 #define _LP64 1 #define __SIZEOF_WCHAR_T__ 4 #define __DEC_EVAL_METHOD__ 2 #define __INTMAX_MAX__ 9223372036854775807L #define __FLT_DENORM_MIN__ 1.40129846e-45F #define _CALL_AIX 1 #define __bgq__ 1 #define __CHAR32_TYPE__ unsigned int #define __FLT_MAX__ 3.40282347e+38F #define __SIZEOF_DOUBLE__ 8 #define __FLT_MIN_10_EXP__ (-37) #define _CALL_AIXDESC 1 #define __INTMAX_TYPE__ long int #define __DEC128_MAX_EXP__ 6145 #define __GNUC_MINOR__ 4 #define __DEC32_MANT_DIG__ 7 #define __DBL_MAX_10_EXP__ 308 #define __LDBL_DENORM_MIN__ 4.94065645841246544176568792868221e-324L #define __STDC__ 1 #define __PTRDIFF_TYPE__ long int #define __DEC64_SUBNORMAL_MIN__ 0.000000000000001E-383DD #define _ARCH_PPC64 1 #define __DEC128_MANT_DIG__ 34 #define __LDBL_MIN_10_EXP__ (-291) #define __SIZEOF_LONG_LONG__ 8 #define __LDBL_DIG__ 31 #define __GNUC_GNU_INLINE__ 1 We may add one of this to the framework to have a correct execution Cheers, ++t Timothée Ewart, Ph. D. http://www.linkedin.com/in/tewart timothee.ewart(a)epfl.ch<mailto:timothee.ewart@epfl.ch>

4 6