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 system is x86_64, 16 c
On Thu, 8 Nov 2018 at 18:31, Alok Priyadarshi wrote:
>
> Jonathan: The system is x86_64, 16 cores, no cpu affinity set. Not too sure
> about load yet.
>
> Mathieu: The explanation makes sense. Running babeltrace with
> --stream-intersection flag did filter out a lot of events. However it is hard
Jonathan: The system is x86_64, 16 cores, no cpu affinity set. Not too sure
about load yet.
Mathieu: The explanation makes sense. Running babeltrace with
--stream-intersection flag did filter out a lot of events. However it is
hard to verify the filtered result because we do not yet know how to re
Hi Alok,
With a snapshot trace, you can end up with some per-cpu buffers that contain
information
going further back in time compared to other per-cpu buffers. This depends on
the level of
system activity and tracing throughput for each CPU.
The situation you experience can very well be tri
> A custom trace event class emits "begin" and "end" events in its
> constructor and destructor respectively. So I do not think this is due to
> conditional path.
If you can guarantee that the destructor is called, seems good to me.
Do you see scenario where the "begin" event is missing ?
>
> S
A custom trace event class emits "begin" and "end" events in its
constructor and destructor respectively. So I do not think this is due to
conditional path.
Sequence of commands to capture a snapshot are:
lttng create --snapshot
lttng enable-event --userspace --all
lttng add-context --userspace -t
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 events did not have corresponding end
> events in the trace.
Seem
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
Hi,
On Wed, Oct 31, 2018 at 02:58:37PM -0700, 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 - KeKriek
>
> Session:
> - Snapshot mode
> - One channel with default
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 - KeKriek
>
> Session:
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
11 matches
Mail list logo
