Uploaded image for project: 'Log4cxx'
  1. Log4cxx
  2. LOGCXX-359

Lock order violation

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 0.10.0
    • None
    • Core
    • None

    Description

      Calling log4cxx::configureAndWatch() results in Logger::mutex being locked first, and Hierarchy::mutex being locked nested.
      Calling log4cxx::LogManager::resetConfiguration() results in Hierarchy::mutex being locked first, and Logger::mutex being locked nested.

      See also attached example and output from helgrind.

      Similar problem as in issue 317.

      Attachments

        1. helgrind-report.txt
          4 kB
          Stefan Röllin
        2. example.cpp
          2 kB
          Stefan Röllin

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. LOGCXX-317 Log4cxx triggers locking inversion, which can result in a deadlock

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              carnold@apache.org Curt Arnold
              stefan_roellin Stefan Röllin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: