[lttng-dev] CTF -> Chrome Trace Event

Hello, I am considering using lttng in my current project. We also like Catapult trace viewer used by chrome://tracing. I am wondering if someone has tried translating CTF tracepoints into Catapult trace events, whose format is described here: https:

[lttng-dev] lttng_ust_cyg_profile

I am trying to collect a trace for visualizing callstack using lttng_ust_cyg_profile. Even though I have compiled a single source file with -finstrument-functions, I guess it is producing too many events to considerably slow down the instrumented process and cause lost events. I am using clang, w

Re: [lttng-dev] lttng_ust_cyg_profile

Response inline. On Thu, Mar 22, 2018 at 12:25 PM Jonathan Rajotte-Julien < jonathan.rajotte-jul...@efficios.com> wrote: > Hi Alok, > > On Thu, Mar 22, 2018 at 06:31:41PM +, Alok Priyadarshi wrote: > > I am trying to collect a trace for visualizing callstack using >

[lttng-dev] Adding thread timestamp to event context

I am trying to add a thread timestamp to trace events. By thread timestamp I mean the value returned by clock_gettime(CLOCK_THREAD_CPUTIME_ID): https://linux.die.net/man/3/clock_gettime I could do this by creating custom events, but I am wondering if there is already a way to add this information

Re: [lttng-dev] Adding thread timestamp to event context

Thanks for your prompt response Mathieu. Can I expect this to happen soonish? On Thu, Oct 25, 2018 at 6:02 AM Mathieu Desnoyers < mathieu.desnoy...@efficios.com> wrote: > - On Oct 24, 2018, at 11:05 PM, Alok Priyadarshi > wrote: > > I am trying to add a thread timestamp t

[lttng-dev] lost trace events

We are tracing a multi-process application that generates high-frequency user-space trace events. Environment: - Ubuntu 16.04 LTS - Lttng 2.10.4 - KeKriek Session: - Snapshot mode - One channel with default config: overwrite=1, subbuf_size=524288, num_subbuf=4 We have noticed that a few events a

Re: [lttng-dev] lost trace events

Any advice on how to debug lost events? Thanks in advance! On Wed, Oct 31, 2018 at 2:58 PM Alok Priyadarshi wrote: > We are tracing a multi-process application that generates high-frequency > user-space trace events. > > Environment: > - Ubuntu 16.04 LTS > - Lttng 2.10.4 - K

Re: [lttng-dev] lost trace events

Hi Jonathan, Thanks for your response. We are tracing function scopes. Each scope emits two events - begin and end. We noticed that some begin events did not have corresponding end events in the trace. I have the trace with this problem available. Would that provide any clue? If not, I will try

Re: [lttng-dev] lost trace events

te: > Hi Alok, > > On Wed, Nov 07, 2018 at 11:53:25AM -0800, Alok Priyadarshi wrote: > > Hi Jonathan, > > > > Thanks for your response. > > > > We are tracing function scopes. Each scope emits two events - begin and > > end. We noticed that some begin e

Re: [lttng-dev] lost trace events

mode in babeltrace. > It ensures that > babeltrace cuts away trace data belonging to time spans that only appear > in some of > the streams. It is not however activated by default. > > To try it out, you can do this: > > babeltrace --stream-intersection path/to/trace > &

Re: [lttng-dev] lost trace events

Awesome, I tried the intersect_mode parameter and it worked. No more lost events. Thanks for your support. On Thu, Nov 8, 2018 at 3:44 PM Jérémie Galarneau < jeremie.galarn...@efficios.com> wrote: > On Thu, 8 Nov 2018 at 18:31, Alok Priyadarshi wrote: > > > > Jonathan: The