Re: [lttng-dev] [PATCH] doc: Fix bind address example for lttng-relayd

On 2020/01/06 09:39, Mathieu Desnoyers wrote: > - On Jan 6, 2020, at 12:19 AM, Benjamin Poirier > benjamin.poir...@gmail.com wrote: > > > INADDR_ANY is 0.0.0.0 > > Hi Benjamin, > > Double-checking this seems to confirm what the man page states: > > %

[lttng-dev] [PATCH] doc: Fix bind address example for lttng-relayd

INADDR_ANY is 0.0.0.0 Fixes: c93eadade277 ("doc/man: use propagated default values in man pages") Signed-off-by: Benjamin Poirier --- doc/man/lttng-relayd.8.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man/lttng-relayd.8.txt b/doc/man/lttng-relayd.8

[lttng-dev] Workflow to view old and current trace data

Hi, long time no see! Consider a system that's recording trace data continuously from a userspace application. A problem is noticed and I'd like to investigate it. What workflow would allow me to view past trace data to analyze the cause of the problem and view current (live) trace data while work

[lttng-dev] [PATCH latency_tracker] Use $(src) rather than pwd to identify the source tree.

This fixes the build when using kernels older than "aa55c8e kbuild: handle C=... and M=... after entering into build directory (v3.18-rc1)" and a separate object output directory (`make O=...`). Signed-off-by: Benjamin Poirier --- Makefile | 2 +- 1 file changed, 1 insertion(+),