1. 19 Apr, 2017 1 commit
  2. 27 Jan, 2017 2 commits
  3. 30 Dec, 2016 1 commit
    • Stefan Sauer's avatar
      info: re-eval GST_DEBUG env var for late categories · ee52459a
      Stefan Sauer authored
      When registering a new debug category after _debug_init(), we need to
      re check the GST_DEBUG filter settings again.
      In addition when parsing the filter setting, we need to already bump up
      the min-debug level to not suppress debug log statments that dynamically
      register a category. This happens in libraries that use a function to
      register a category on first use.
      ee52459a
  4. 13 Dec, 2016 1 commit
  5. 12 Dec, 2016 1 commit
    • Thibault Saunier's avatar
      info: Add a 'flags' parametter to gst_debug_get_stack_trace · 33616d47
      Thibault Saunier authored
      This is an API break but that API has not been released yet.
      
      We are passing a flag rather than a simple boolean as we can imagine
      to implement more features in the future for example to retrieve a
      stack trace for all the threads, etc..
      
      Retrieving source file and line numbers is pretty
      expensive while getting a stack trace, this new argument
      allows the user to decide to retrieve a backtrace
      without those infos instead which is much faster.
      
      For example running $ GST_LEAKS_TRACER_STACK_TRACE=1 GST_DEBUG=GST_TRACER:7 \
      GST_TRACERS=leaks time gst-launch-1.0 videotestsrc num-buffers=1 ! fakesink:
      
      * With simple stack traces:
      
          0.04s user 0.02s system 99% cpu 0.060 total
      
      * With full stack traces:
      
          0.66s user 0.23s system 96% cpu 0.926 total
      
      https://bugzilla.gnome.org/show_bug.cgi?id=775423
      33616d47
  6. 06 Dec, 2016 1 commit
  7. 12 Nov, 2016 1 commit
  8. 11 Nov, 2016 1 commit
  9. 04 Nov, 2016 2 commits
  10. 01 Nov, 2016 1 commit
    • Stian Selnes's avatar
      info: Replace %p and %r in GST_DEBUG_FILE · 287645c2
      Stian Selnes authored
      It's useful to be able to set a name pattern for GST_DEBUG_FILE so that
      the same environment variable can be used for multiple processes and
      still write to different files. Especially useful if these processes
      run simultaneously.
      
      %p: Replaced with PID
      %r: Replaced with random number
      
      %p is obviously useful. %r is useful when for instance running two
      processes with same PID but in different containers.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=773092
      287645c2
  11. 26 Aug, 2016 1 commit
  12. 02 Apr, 2016 1 commit
  13. 26 Mar, 2016 1 commit
  14. 15 Feb, 2016 1 commit
  15. 20 Jan, 2016 1 commit
  16. 13 Jan, 2016 1 commit
    • Matthew Waters's avatar
      info: expose debugging printf functions · 347734e5
      Matthew Waters authored
      Other gst libraries and/or elements may want to add some debug logging to an
      external debug system or implement delayed debugging for performance reasons.
      
      Exposes the internal __gst_vasprintf as gst_info_vasprintf which has a fallback
      to g_vasprintf if the debug system is disabled.
      
      API: gst_info_vasprintf
      API: gst_info_strdup_vprintf
      API: gst_info_strdup_printf
      
      https://bugzilla.gnome.org/show_bug.cgi?id=760421
      347734e5
  17. 08 Jan, 2016 1 commit
  18. 07 Jan, 2016 1 commit
  19. 23 Apr, 2015 1 commit
  20. 18 Apr, 2015 1 commit
    • Alex Ashley's avatar
      protection: add GstProtectionMeta to support protected content · abdafb0d
      Alex Ashley authored
      In order to support some types of protected streams (such as those
      protected using DASH Common Encryption) some per-buffer information
      needs to be passed between elements.
      
      This commit adds a GstMeta type called GstProtectionMeta that allows
      protection specific information to be added to a GstBuffer. An example
      of its usage is qtdemux providing information to each output sample
      that enables a downstream element to decrypt it.
      
      This commit adds a utility function to select a supported protection
      system from the installed Decryption elements found in the registry.
      The gst_protection_select_system function that takes an array of
      identifiers and searches the registry for a element of klass Decryptor that
      supports one or more of the supplied identifiers. If multiple elements
      are found, the one with the highest rank is selected.
      
      This commit adds a unit test for the gst_protection_select_system
      function that adds a fake Decryptor element to the registry and then
      checks that it can correctly be selected by the utility function.
      
      This commit adds a unit test for GstProtectionMeta that creates
      GstProtectionMeta and adds & removes it from a buffer and performs some
      simple reference count checks.
      
      API: gst_buffer_add_protection_meta()
      API: gst_buffer_get_protection_meta()
      API: gst_protection_select_system()
      API: gst_protection_meta_api_get_type()
      API: gst_protection_meta_get_info()
      
      https://bugzilla.gnome.org/show_bug.cgi?id=705991
      abdafb0d
  21. 06 Apr, 2015 1 commit
  22. 12 Mar, 2015 1 commit
  23. 10 Mar, 2015 1 commit
  24. 05 Mar, 2015 3 commits
  25. 16 Feb, 2015 1 commit
  26. 01 Dec, 2014 1 commit
  27. 25 Sep, 2014 1 commit
    • Tim-Philipp Müller's avatar
      info: remove confusing warning about running under valgrind · 70d692c4
      Tim-Philipp Müller authored
      We're not actually doing anything differently anywhere when
      we detect that we're running under valgrind, so let's not
      print that confusing message that makes people wonder how
      they can switch it off so they can valgrind the normal
      code paths. Seeing that we're not doing that nor have done
      so in the last 10 years we might just as well remove the
      entire check actually.
      70d692c4
  28. 17 Sep, 2014 1 commit
    • Stefan Sauer's avatar
      info: avoid global variable for log_file · a528dadb
      Stefan Sauer authored
      Use user_data to pass the log_file handle to the logger-function.
      
      If one wants to change the log target (e.g. GST_DEBUG_FILE), simply call
      gst_debug_remove_log_function() and re-add the handler with the new log-target
      using gst_debug_add_log_function ().
      a528dadb
  29. 03 Jun, 2014 4 commits
  30. 29 May, 2014 1 commit
  31. 27 Feb, 2014 1 commit
  32. 16 Jan, 2014 1 commit
  33. 08 Jan, 2014 1 commit