Commit 0b9b8c76 authored by Guillaume Desmottes's avatar Guillaume Desmottes 🐐 Committed by Tim-Philipp Müller

docs: fix GST_LEAKS_TRACER_SIG doc

The documentation wasn't mentioning the SIGUSR2 signal.

https://bugzilla.gnome.org/show_bug.cgi?id=772571
parent d02e1d7f
...@@ -264,9 +264,9 @@ leaks ...@@ -264,9 +264,9 @@ leaks
----- -----
- track creation/destruction of GstObject and GstMiniObject - track creation/destruction of GstObject and GstMiniObject
- log those which are still alive when app is exiting and raise an error if any - log those which are still alive when app is exiting and raise an error if any
- If the GST_LEAKS_TRACER_SIG env variable is defined: - If the GST_LEAKS_TRACER_SIG env variable is defined the tracer will handle the following UNIX signals:
- log alive objects when receiving the SIGUSR1 signal. - SIGUSR1: log alive objects
- create a checkpoint and print a list of objects created and destroyed since - SIGUSR2: create a checkpoint and print a list of objects created and destroyed since
the previous checkpoint. the previous checkpoint.
- If the GST_LEAKS_TRACER_STACK_TRACE env variable is defined log the creation - If the GST_LEAKS_TRACER_STACK_TRACE env variable is defined log the creation
stack trace of leaked objects. This may significantly increase memory stack trace of leaked objects. This may significantly increase memory
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment