Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: matthieu.castet@parrot.com (Matthieu CASTET)
Subject: [ltt-dev] Tracing thread name
Date: Tue, 4 Aug 2009 12:12:43 +0200	[thread overview]
Message-ID: <4A78099B.4@parrot.com> (raw)
In-Reply-To: <20090803134843.GB23455@Krystal>

Hi Mathieu,

Mathieu Desnoyers a ?crit :
> * Matthieu CASTET (matthieu.castet at parrot.com) wrote:
>> Hi,
>>
>> I use ltt on a 2.6.27 on an arm architecture.
>> It works quite well, but I have a minor problem :
>>
>> my application sets thread name with prctl PR_SET_NAME. But ltt viewer
>> doesn't seem to saw it.
>>
> 
> Hrm, I guess we might want to instrument set_task_comm as you propose to
> get the correct process name, but if this gets us the thread name, I
> think it's only an implementation side-effect:

> The way LTTng handles thread names is by adding a userspace "thread
> branding" event. It should be executed at thread startup. The downside
> of the current LTTng approach is that we cannot know the name of threads
> already executing before we started tracing.
> 

Do you know if it is possible to patch my version to add such feature ?

I saw that the name already change in the trace before/after an exec.
How lltv get the new name ?
With "fs.exec" tracepoint ?
In that case I could fake a "fs.exec" tracepoint in set_task_comm.

Thanks

Matthieu




  parent reply	other threads:[~2009-08-04 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 13:20 [ltt-dev] ltt comm tracking Matthieu CASTET
2009-08-03 13:48 ` [ltt-dev] Tracing thread name (was: ltt comm tracking) Mathieu Desnoyers
2009-08-03 14:28   ` Peter Zijlstra
2009-08-04 10:12   ` Matthieu CASTET [this message]
2009-08-04 13:05     ` [ltt-dev] Tracing thread name Mathieu Desnoyers
2009-08-04 14:06       ` Matthieu CASTET
2009-08-13 15:57         ` Matthieu CASTET

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=4A78099B.4@parrot.com \
    --to=matthieu.castet@parrot.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