1. 11 2月, 2020 5 次提交
  2. 09 2月, 2020 1 次提交
  3. 04 2月, 2020 2 次提交
  4. 29 1月, 2020 1 次提交
  5. 10 1月, 2020 1 次提交
  6. 03 1月, 2020 2 次提交
  7. 10 12月, 2019 2 次提交
  8. 09 12月, 2019 5 次提交
  9. 04 12月, 2019 1 次提交
  10. 20 11月, 2019 1 次提交
  11. 15 11月, 2019 2 次提交
  12. 12 11月, 2019 1 次提交
  13. 25 10月, 2019 1 次提交
  14. 21 10月, 2019 2 次提交
  15. 18 10月, 2019 2 次提交
    • D
      util: drop logging filter/output flags · 5722e26e
      Daniel P. Berrangé 提交于
      With the removal of support for log message stack traces, there is
      nothing using the logging filter/output flags and they can be removed.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      5722e26e
    • D
      util: drop support for stack traces with logging · 9b80e0c1
      Daniel P. Berrangé 提交于
      The log filters have supported the use of a "+" before the source match
      string to request that a stack trace be emitted for every log message:
      
        commit 54856395
        Author: Daniel P. Berrange <berrange@redhat.com>
        Date:   Wed May 9 15:18:56 2012 +0100
      
          Allow stack traces to be included with log messages
      
          Sometimes it is useful to see the callpath for log messages.
          This change enhances the log filter syntax so that stack traces
          can be show by setting '1:+NAME' instead of '1:NAME'.
      
      With the huge & ever increasing number of logging statements per file,
      this will be incredibly verbose and have a major performance penalty.
      This makes the feature impractical to use widely and as such it is not
      worth the code maint cost.
      
      Removing this seldom used feature allows us to drop the 'execinfo'
      module in gnulib which provides the backtrace() function which doesn't
      exist on non-Linux.
      
      Users who want to get stack traces of parts of libvirt can use GDB,
      or systemtap for live tracing with minimal perf impact.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      9b80e0c1
  16. 16 10月, 2019 1 次提交
  17. 15 10月, 2019 2 次提交
  18. 14 10月, 2019 1 次提交
  19. 19 9月, 2019 1 次提交
  20. 13 9月, 2019 1 次提交
  21. 10 9月, 2019 1 次提交
    • D
      util: activate directory override when used from library · b1b878c5
      Daniel P. Berrangé 提交于
      The Perl bindings for libvirt use the test driver for unit tests. This
      tries to load the cpu_map/index.xml file, and when run from an
      uninstalled build will fail.
      
      The problem is that virFileActivateDirOverride is called by our various
      binaries like libvirtd, virsh, but is not called when a 3rd party app
      uses libvirt.so
      
      To deal with this we allow the LIBVIRT_DIR_OVERRIDE=1 env variable to be
      set and make virInitialize look for this. The 'run' script will set it,
      so now build using this script to run against an uninstalled tree we
      will correctly resolve files to the source tree.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      b1b878c5
  22. 27 8月, 2019 1 次提交
  23. 23 8月, 2019 1 次提交
    • R
      tests: Add lib- prefix to all mocks · fde36108
      Roman Bolshakov 提交于
      In preparation libtool "-module" flag removal, add lib prefix to all
      mock shared objects.
      
      While at it, introduce VIR_TEST_MOCK macros that makes path out of mock
      name to be used with VIR_TEST_PRELOAD or VIR_TEST_MAIN_PRELOAD.  That,
      hopefully, improves readability, reduces line length and allows to
      tailor VIR_TEST_MOCK for specific platform if it has shared library
      suffix different from ".so".
      Signed-off-by: NRoman Bolshakov <r.bolshakov@yadro.com>
      fde36108
  24. 14 3月, 2019 1 次提交
  25. 07 3月, 2019 1 次提交