t trace process:
trace@trace:~/cc$ sudo lttng create instrument
Session instrument created.
Traces will be output to /root/lttng-traces/instrument-20200623-222917
trace@trace:~/cc$ sudo lttng enable-channel user_func_trace --userspace
UST channel user_func_trace enab
ce@trace:~/cc$ sudo lttng create instrument
Session instrument created.
Traces will be output to /root/lttng-traces/instrument-20200623-222917
trace@trace:~/cc$ sudo lttng enable-channel user_func_trace --userspace
UST channel user_func_trace enabled for session instr
so
> ./instrument
>
>4. start trace process:
>trace@trace:~/cc$ sudo lttng create instrument
>Session instrument created.
>Traces will be output to
> /root/lttng-traces/instrument-20200623-222917
>
>trace@trace:~/cc$ sudo lttng enable-channel
2. build source code:
>$ gcc -g -finstrument-functions instrument.c -o instrument
> 3. run program:
> $
>LD_PRELOAD=/usr/lib/x86_64-linux-gnu/liblttng-ust-cyg-profile.so
>./instrument
> 4. start trace process:
> trace@tra
On 12:52 Tue 23 Jun, Christophe Bédard wrote:
>Hi,
>
> Babeltrace is doing exactly what it should as far as I know.
>
>yes, but babeltrace can provide the information if:
>* ip and vpid contexts are enabled (for userspace), e.g.
>
>$ lttng add-context --userspace --type=ip -
