Dear Alex,
Thanks for your attention. I executed your commands step by step. While, again
I received previous errors which areĀ
[error] Cannot open any trace for reading.[error] opening trace
"[path]/lttng-traces/auto-20171011-145947" for reading.
[error] none of the specified trace p
Hi,
2017-10-11 17:10 GMT-04:00 avkumar :
>
> Perf probes:
> How can we add the dynamic trace points created by perf probe into lttng?
> When I add the perf probe as kprobe type I get missing tracepoint error, If I
> add the perf probe as tracepoint , Lttng does not complain
Perf probes:
How can we add the dynamic trace points created by perf probe into lttng?
When I add the perf probe as kprobe type I get missing tracepoint error, If
I add the perf probe as tracepoint , Lttng does not complain but it does
not collect any data when the tracepoint is hit.
perf probe
Hi,
On Thu, Sep 28, 2017 at 04:57:42PM -0400, Jonathan Rajotte-Julien wrote:
> Hi Liguang,
>
> Thanks for submitting the patch.
>
> On Wed, Sep 27, 2017 at 05:57:59PM +0800, Liguang Li wrote:
> > When setup metadata failed, the exception handling function will free
> > the metadata stream
Hi,
> > > I think the root cause is that the parsing and printing process is a bit
> > slow. So i want to know if there
> > > are any method to improve the performance of this process.
> >
> > A simple experiment would be to run a bounded workload
> > to perform a quick timing evaluation of
ttng start
$ java -cp /usr/share/java/lttng-ust-agent-jul.jar:. Hello
$ lttng stop
$ lttng view
and I get the following output:
Trace directory: /home/alexandre/lttng-traces/auto-20171011-102431
[10:24:49.326824061] (+?.?) calista lttng_jul:event: { cpu_id =
2 }, { msg = "Hello World, t
Hi,
On Thu, Sep 21, 2017 at 11:03 PM, Jonathan Rajotte Julien <
jonathan.rajotte-jul...@efficios.com> wrote:
> Hi,
>
> On 2017-09-21 05:34 AM, liguang li wrote:
> > Hi,
> >
> > On Wed, Sep 20, 2017 at 10:58 PM, Jonathan Rajotte Julien <
> jonathan.rajotte-jul...@efficios.com