Opened 7 years ago

Closed 5 years ago

#2424 closed defect (wontfix)

seg fault in src/bin/auth/tests

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: Unclassified Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

On my NetBSD 6.0 system with log4cplus 1.1.0 built --without-threads (see #2423), sometimes make check fails in src/bin/auth/tests/.

One example is:

[ RUN      ] AuthSrvTest.DDNSForwardClose
log4cplus:ERROR Error in strftime(): 0
[1]   Segmentation fault (core dumped) B10_FROM_BUILD=/...
*** Error code 139

It has also failed in AuthSrvTest?.DDNSForwardCreateDestroy and also failed when all tests complete. It cored about 7 out of 45 tries.

Here is a backtrace:

Reading symbols from /home/reed/work/isc/bind10/git/bind10-CLEAN/src/bin/auth/tests/.libs/run_unittests...done.
[New process 77]
[New process 76]
[New process 1]
Core was generated by `run_unittests'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f7ff484c328 in log4cplus::helpers::Time::getFormattedTime(std::string const&, bool) const () from /usr/pkg/lib/liblog4cplus-1.1.so.5
(gdb) bt
#0  0x00007f7ff484c328 in log4cplus::helpers::Time::getFormattedTime(std::string const&, bool) const () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#1  0x00007f7ff48413ac in ?? () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#2  0x00007f7ff4841c80 in ?? () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#3  0x00007f7ff4841ebb in log4cplus::PatternLayout::formatAndAppend(std::ostream&, log4cplus::spi::InternalLoggingEvent const&) ()
   from /usr/pkg/lib/liblog4cplus-1.1.so.5
#4  0x00007f7ff482de6a in log4cplus::FileAppender::append(log4cplus::spi::InternalLoggingEvent const&) () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#5  0x00007f7ff482554c in log4cplus::Appender::doAppend(log4cplus::spi::InternalLoggingEvent const&) () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#6  0x00007f7ff48223be in log4cplus::helpers::AppenderAttachableImpl::appendLoopOnAppenders(log4cplus::spi::InternalLoggingEvent const&) const ()
   from /usr/pkg/lib/liblog4cplus-1.1.so.5
#7  0x00007f7ff483b613 in log4cplus::spi::LoggerImpl::callAppenders(log4cplus::spi::InternalLoggingEvent const&) () from /usr/pkg/lib/liblog4cplus-1.1.so.5
#8  0x00007f7ff540e78c in isc::log::LoggerImpl::outputRaw (
    this=0x7f7ff7b56580, severity=<optimized out>, message=<optimized out>)
    at logger_impl.cc:141
#9  0x000000000042ed88 in ~Formatter (this=0x7f7ff13ffa00, 
    __in_chrg=<optimized out>) at ../../../../src/lib/log/log_formatter.h:167
#10 isc::auth::datasrc_clientmgr_internal::DataSrcClientsBuilderBase<isc::util::thread::Mutex, isc::util::thread::CondVar>::run (this=0x7f7ff7bbd528)
    at ../../../../src/bin/auth/datasrc_clients_mgr.h:473
#11 0x00007f7ff32086ba in operator() (this=0x7f7ff7b674d8)
    at /usr/pkg/include/boost/function/function_template.hpp:760
#12 isc::util::thread::Thread::Impl::run (impl_raw=0x7f7ff7b674d0)
    at thread.cc:71
#13 0x00007f7ff2609d75 in ?? () from /usr/lib/libpthread.so.1
#14 0x00007f7ff1a759f0 in ___lwp_park50 () from /usr/lib/libc.so.12
Cannot access memory at address 0x7f7ff1400000
(gdb) info threads 
  Id   Target Id         Frame 
* 1    LWP 1             0x00007f7ff484c328 in log4cplus::helpers::Time::getFormattedTime(std::string const&, bool) const ()
   from /usr/pkg/lib/liblog4cplus-1.1.so.5

The current thread <Thread ID 1> has terminated.  See `help thread'.

Subtickets

Change History (4)

comment:1 Changed 7 years ago by jelte

  • Estimated Difficulty changed from undecided to 5

Setting this to 5; we do not know if this is easy or hard to fix. Please do not spend any more time on this than that limit; if it is not fixable within that time, spend the time of this ticket devising how to fix it (and we'll do that in another ticket)

comment:2 Changed 7 years ago by shane

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.