Thanks for the tips. The stopping/starting issue (resulting in no more events)
still exists with a live session, but it is related to Trace Compass reading
the logs, not LTTng writing them. The logs are still written to and Babeltrace
can view them fine, but Trace Compass cannot view past the po
For lttng-ust, can I put the tracepoint definition in two files, but they
use the same provider.
Thank you.
Yonghong
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
I am not sure whether this is a bug or the wrong I am using it. When I use
extern declaration as follows, I always have compilation error. I used the
easy-ust to demonstrate:
*diff --git a/doc/examples/easy-ust/sample_component_provider.h
b/doc/examples/easy-ust/sample_component_provider.h*
*inde
- On Oct 7, 2019, at 12:06 PM, Yonghong Yan yany...@gmail.com wrote:
> I am not sure whether this is a bug or the wrong I am using it. When I use
> extern declaration as follows, I always have compilation error. I used the
> easy-ust to demonstrate:
> diff --git a/doc/examples/easy-ust/samp
- On Oct 7, 2019, at 9:59 AM, Yonghong Yan yany...@gmail.com wrote:
> For lttng-ust, can I put the tracepoint definition in two files, but they use
> the same provider.
Based on the terminology here:
https://lttng.org/docs/v2.10/#doc-tracing-your-own-user-application
You need to have at
Thank you.
I got most. To confirm, I have two header files, each defines its own
tracepoint, they are from the same provider. The source files that use the
header files have its own #define TRACEPOINT_CREATE_PROBES and #define
TRACEPOINT_DEFINE. This won't work since two files have those defines.
- On Oct 7, 2019, at 12:42 PM, Yonghong Yan wrote:
> Thank you.
> I got most. To confirm, I have two header files, each defines its own
> tracepoint, they are from the same provider. The source files that use the
> header files have its own #define TRACEPOINT_CREATE_PROBES and #define
> TRA
