Opened 8 years ago
Closed 7 years ago
#11109 closed Bugs (invalid)
using 1.57 boost log mechanism and hang at the following
Reported by: | Owned by: | Andrey Semashev | |
---|---|---|---|
Milestone: | To Be Determined | Component: | log |
Version: | Boost 1.57.0 | Severity: | Problem |
Keywords: | Cc: |
Description
#0 0x00007f6dffe66fce in lll_lock_wait_private () from /opt/huawei-data-protection/cloudprotector/libs/libc.so.6 #0 0x00007f6dffe66fce in lll_lock_wait_private () from /opt/huawei-data-protection/cloudprotector/libs/libc.so.6 #1 0x00007f6dffe18abd in _L_lock_1598 () from /opt/huawei-data-protection/cloudprotector/libs/libc.so.6 #2 0x00007f6dffe18876 in tz_convert () from /opt/huawei-data-protection/cloudprotector/libs/libc.so.6 #3 0x00000000005c3ee5 in localtime (result=0x7f6de77fd6c0, t=0x7f6de77fd698) at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/date_time/c_time.hpp:67 #4 create_time (converter=0x5bfee0 <boost::date_time::c_time::localtime(long const*, tm*)>)
at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/date_time/microsec_time_clock.hpp:100
#5 local_time () at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/date_time/microsec_time_clock.hpp:70 #6 get_clock () at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/log/attributes/time_traits.hpp:69 #7 boost::log::v2_mt_posix::attributes::basic_clock<boost::log::v2_mt_posix::attributes::local_time_traits>::impl::get_value (this=<optimized out>)
at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/log/attributes/clock.hpp:63
#8 0x00007f6e0188cf47 in boost::log::v2_mt_posix::attribute_value_set::freeze() () from /opt/huawei-data-protection/cloudprotector/libs/libboost_log.so.1.57.0 #9 0x00007f6e018904a0 in boost::log::v2_mt_posix::core::open_record(boost::log::v2_mt_posix::attribute_set const&) () from /opt/huawei-data-protection/cloudprotector/libs/libboost_log.so.1.57.0 #10 0x00000000005b0d8f in open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log::v2_mt_posix::keywords::tag::severity, severity_level const> > (this=0x116abe8)
at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/log/sources/basic_logger.hpp:259
#11 open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log::v2_mt_posix::keywords::tag::severity, severity_level const> > (args=..., this=0x116abe8)
at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/log/sources/severity_feature.hpp:253
#12 boost::log::v2_mt_posix::sources::basic_composite_logger<char, boost::log::v2_mt_posix::sources::severity_logger_mt<severity_level>, boost::log::v2_mt_posix::sources::multi_thread_model<boost::log::v2_mt_posix::aux::light_rw_mutex>, boost::log::v2_mt_posix::sources::features<boost::log::v2_mt_posix::sources::severity<severity_level>, void, void, void, void, void, void, void, void, void> >::open_record<boost::parameter::aux::tagged_argument<boost::log::v2_mt_posix::keywords::tag::severity, severity_level const> > (this=0x116abe8, args=...) at /usr1/code/HCP_V100R001_SP3/code/current/HCP_V1R1_Code/V100R001C01/open_src/boost/boost_1_57_0/lib/include/boost/log/sources/basic_logger.hpp:459
Change History (3)
comment:1 by , 8 years ago
Component: | None → log |
---|---|
Owner: | set to |
comment:2 by , 8 years ago
comment:3 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
In the backtrace, I can only see libc lock being locked, which Boost.Log doesn't access itself. Please, provide more information on the problem, preferably with a minimal reproducing code sample.