From 0b9b8c768c716957351b44d4be45822c19479686 Mon Sep 17 00:00:00 2001 From: Guillaume Desmottes Date: Fri, 7 Oct 2016 17:02:47 +0200 Subject: [PATCH] docs: fix GST_LEAKS_TRACER_SIG doc The documentation wasn't mentioning the SIGUSR2 signal. https://bugzilla.gnome.org/show_bug.cgi?id=772571 --- docs/design/part-tracing.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/design/part-tracing.txt b/docs/design/part-tracing.txt index e396474014..655f46daaa 100644 --- a/docs/design/part-tracing.txt +++ b/docs/design/part-tracing.txt @@ -264,9 +264,9 @@ leaks ----- - track creation/destruction of GstObject and GstMiniObject - 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: - - log alive objects when receiving the SIGUSR1 signal. - - create a checkpoint and print a list of objects created and destroyed since +- If the GST_LEAKS_TRACER_SIG env variable is defined the tracer will handle the following UNIX signals: + - SIGUSR1: log alive objects + - SIGUSR2: create a checkpoint and print a list of objects created and destroyed since the previous checkpoint. - If the GST_LEAKS_TRACER_STACK_TRACE env variable is defined log the creation stack trace of leaked objects. This may significantly increase memory