[lttng-dev] Enabling Syscalls LTTng v2.5.1

Dilong Zheng Dilong.Zheng at mitel.com
Fri Jul 10 08:51:32 EDT 2015


https://bugs.lttng.org/issues/644 <- thats the link I read from. I have not yet trie with the latest 2.5.x release I will soon though.


Thanks,


Dilong

________________________________
From: jeremie.galarneau at gmail.com <jeremie.galarneau at gmail.com> on behalf of Jérémie Galarneau <jeremie.galarneau at efficios.com>
Sent: Thursday, July 9, 2015 10:36 AM
To: Dilong Zheng
Cc: lttng-dev at lists.lttng.org
Subject: Re: Enabling Syscalls LTTng v2.5.1


On Jul 9, 2015 9:23 AM, "Dilong Zheng" <Dilong.Zheng at mitel.com<mailto:Dilong.Zheng at mitel.com>> wrote:
>
> Hi Jeremie,
>
>
> I am attempting to enable syscalls by doing: lttng enable-event -a -k --syscall but I am received a warning: "Warning: Kernel events already enabled". From searching online, I read that the warning is just a UI issue and doesn't actually

Can you provide a link to this?
Have you tried with the latest 2.5.x release?

Thanks,
Jérémie

affect the functionality of LTTng; that the syscalls are actually being enabled. However when viewing the kernel trace inside TraceCompass or Tracealyzer I do barely ever see any system calls. The only syscalls that appear if any are almost always "clone". I am currently using Fedora 22, x86 architecture. Be great to get some insight regarding the warning and what I could be doing better to see syscalls by enabling the event. Thanks for your help.
>
>
> Dilong Zheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150710/faa5775e/attachment.html>


More information about the lttng-dev mailing list