Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Thread names in LTTV-gui
Date: Fri, 1 Apr 2011 11:24:54 -0400	[thread overview]
Message-ID: <BLU0-SMTP14238E96F46E2E6BFB777B96BE0@phx.gbl> (raw)
In-Reply-To: <AANLkTinBscJfKXizP2R1noC5s83_u5U866MqRt4zwXf0@mail.gmail.com>

* Ali G?nhan Aky?rek (aliakyurek at gmail.com) wrote:
> Hi all,
> 
> I use the following triple and the kernel 2.6.31.6
> lttng: 0.173
> lttv: 0.12.29
> ltt-control: 0.81
> 
> When I start my application and then start ltt deamon, I see the names of
> the threads created by my application the under Process column of control
> flow viewer in the lttv gui analyzer.

Because this uses the "enum_process_state", triggered by the events
saved by the statedump module executed at trace start to gather various
information about processes and other resources. For the process, I
think it uses its "comm" name as string identifier for process name.

> 
> But if i start lttd deamon first and then start my application later, I see
> the executable name of my application for all threads in the gui.
> Do you have an idea, how i can solve it?

Hrm, I think you might want to consider instrumenting prctl() system
call (see prctl(2)). The one you are interested into is, I think
"PR_SET_NAME". I'm not entirely sure, but it should do. If this works,
we might consider pulling this new instrumentation point in the lttng
project.

Currently, we only use "exec()" instrumentation to get the process name.
I would only make sense to allow be sensitive to the explicit name
changes done by prctl.

Thanks,

Mathieu

> 
> Thanks,
> Best regards,
> Ali

> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




      parent reply	other threads:[~2011-04-01 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 11:12 Ali Günhan Akyürek
2011-04-01 11:12 ` Ali Günhan Akyürek
2011-04-01 11:12 ` Ali Günhan Akyürek
2011-04-01 15:24 ` Mathieu Desnoyers [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=BLU0-SMTP14238E96F46E2E6BFB777B96BE0@phx.gbl \
    --to=compudj@krystal.dyndns.org \
    /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