From: David.OShea@quantum.com (David OShea)
Subject: [lttng-dev] Wrong procname for userspace trace of app with different thread names
Date: Thu, 25 Oct 2012 04:07:54 +0000 [thread overview]
Message-ID: <20998D40D9A2B7499CA5A3A2666CB1EB19F81C78@ZURMSG1.QUANTUM.com> (raw)
In-Reply-To: <20121024130601.GA10310@Krystal>
Hi Mathieu,
> -----Original Message-----
> From: Mathieu Desnoyers [mailto:mathieu.desnoyers@efficios.com]
> Sent: Wednesday, 24 October 2012 11:36 PM
> To: David OShea
> Cc: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] Wrong procname for userspace trace of app with
> different thread names
> > I expect that typical use-cases involve calling prctl right after the
> > thread starts, so it might just work (this would need to be
> documented
> > though).
>
> Please try with lttng-ust HEAD, which includes: [...]
>
> commit 009745db8ca05f7a3abbb37558b08eae0107f7e1
Thanks, I just applied that commit as a patch to the older version of lttng-ust I'm using and it works as desired! I think the assumption that prctl() is called right after the thread starts is a reasonable one.
> > > > Incidentally, why do I have to do "enable-channel" to get the context
> > > > to actually appear? If I don't do this, the "add-context" still says
> > > > that each of the four contexts was "added to all channels", but they
> > > > don't appear in 'lttng view'.
> > >
> > > Please provide the full list of commands you do to reproduce a "good"
> > > and "bad" behavior.
Thanks, I'll do a few tests and make a separate post about this.
Regards,
David
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
prev parent reply other threads:[~2012-10-25 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 3:58 David OShea
2012-10-24 12:32 ` Mathieu Desnoyers
2012-10-24 12:35 ` Mathieu Desnoyers
2012-10-24 13:06 ` Mathieu Desnoyers
2012-10-25 4:07 ` David OShea [this message]
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=20998D40D9A2B7499CA5A3A2666CB1EB19F81C78@ZURMSG1.QUANTUM.com \
--to=david.oshea@quantum.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