From: francis.giraldeau@gmail.com (Francis Giraldeau)
Subject: [lttng-dev] Add pid context to UST events
Date: Fri, 01 Jun 2012 14:22:28 +0200 [thread overview]
Message-ID: <4FC8B404.2080403@gmail.com> (raw)
Hi,
I tried to add pid context to UST events to distinguish events from
multiple processes. I do have this error:
$ lttng create bidon
Session bidon created.
Traces will be written in /home/francis/lttng-traces/bidon-20120601-142031
$ lttng enable-event -a -u
All UST events are enabled in channel channel0
$ lttng add-context -u -t pid
Error: pid: UST invalid context
Warning: Some command(s) went wrong
Am I doing something wrong?
Thanks!
Francis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4476 bytes
Desc: Signature cryptographique S/MIME
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120601/2a171b87/attachment.bin>
next reply other threads:[~2012-06-01 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 12:22 Francis Giraldeau [this message]
2012-06-01 15:53 ` Mathieu Desnoyers
2012-06-01 17:02 ` Bernd Hufmann
2012-06-01 17:14 ` Mathieu Desnoyers
2012-06-01 17:18 ` Bernd Hufmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC8B404.2080403@gmail.com \
--to=francis.giraldeau@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox