Guillaume Desmottes e4cba8a0bf tracers: set MAY_BE_LEAKED on tracer records ... The records are static and so appear as false positives when using those tracers with the leaks tracer as well. The leaks tracer was already setting this flag on its record so let's set it on the other ones as well.		2019-08-02 13:07:58 +05:30
..
.gitignore	tracer: initial prototype for the tracing subsystem	2015-10-05 20:59:39 +02:00
gstlatency.c	tracers: set MAY_BE_LEAKED on tracer records	2019-08-02 13:07:58 +05:30
gstlatency.h	tracer: latency: Show per-element reported latency	2019-04-08 12:28:07 -04:00
gstleaks.c	leakstracer: Improve notes in the the get-live-objects API docs	2019-07-02 15:13:26 +05:30
gstleaks.h	leakstracer: Add API for tracking and checkpointing objects	2019-07-02 15:13:26 +05:30
gstlog.c	tracers: Allow setting a name for all tracer objects	2019-07-02 15:13:26 +05:30
gstlog.h	tracer: split into tracer and tracerutils	2015-10-05 20:59:39 +02:00
gstrusage.c	tracers: set MAY_BE_LEAKED on tracer records	2019-08-02 13:07:58 +05:30
gstrusage.h	tracers: code cleanups	2015-10-05 20:59:39 +02:00
gststats.c	tracers: set MAY_BE_LEAKED on tracer records	2019-08-02 13:07:58 +05:30
gststats.h	tracers: code cleanups	2015-10-05 20:59:39 +02:00
gsttracers.c	tracers: add leaks tracer	2016-06-03 00:36:46 +01:00
Makefile.am	tracers: log: no need to link to our internal printf implementation	2017-11-26 11:14:01 +00:00
meson.build	docs: add coretracers to the list of plugins	2019-05-18 02:41:43 +00:00