From: ajitrzid@yahoo.com (Ajit R)
Subject: [ltt-dev] Change process name to be command line
Date: Thu, 27 Aug 2009 03:31:17 -0700 (PDT) [thread overview]
Message-ID: <458481.77854.qm@web63205.mail.re1.yahoo.com> (raw)
In-Reply-To: <7660C7A486834C48B1487748EA32BCA362B40FBB06@spec-ty-exch.fihspec.com>
Hi
--- On Thu, 8/27/09, Bryan Hsieh <bryanhsieh at fihspec.com> wrote:
> From: Bryan Hsieh <bryanhsieh@fihspec.com>
> Subject: [ltt-dev] Change process name to be command line
> To: "'ltt-dev at lists.casi.polymtl.ca'" <ltt-dev at lists.casi.polymtl.ca>
> Date: Thursday, August 27, 2009, 2:26 PM
> Hi All,
>
> My user space process name are all the same - "app_process"
> in LTTV, I'd like to distinguish with them, it seems LTT cat
> from /proc/[number]/stat. I'd like to change to be command
> line from /proc/[number]/cmdline when the process name is
> specific name or just like what the busybox implement in PS,
> where can I modify in LTT patch?
> Thank you very much!
>
> Best regards,
> Bryan Hsieh
_______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
You could change the app names by using the prctl system call.
This works for threads too. Refer to this discussion on the ltt-dev
about how you can get thread/process names and can be seen by ltt:
http://lists.casi.polymtl.ca/pipermail/ltt-dev/2009-August/001859.html
Also if you have an older ltt implementation you might have to
use the marker differently, in "set_task_comm" add this line
trace_mark(fs_exec, "filename %s", tsk->comm).
In Busybox too you would have to enable code to use the task
structure's "comm" field printing.
Regards
Ajit
prev parent reply other threads:[~2009-08-27 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7660C7A486834C48B1487748EA32BCA3503EE618A8@spec-ty-exch.fihspec.com>
[not found] ` <345025.22508.qm@web63207.mail.re1.yahoo.com>
[not found] ` <7660C7A486834C48B1487748EA32BCA3503EE618AA@spec-ty-exch.fihspec.com>
[not found] ` <20090731154237.GA8847@Krystal>
2009-08-04 8:28 ` [ltt-dev] Some LTTng 0.43 issue on ARM Bryan Hsieh
2009-08-04 8:28 ` Bryan Hsieh
2009-08-04 8:28 ` Bryan Hsieh
2009-08-04 13:18 ` Mathieu Desnoyers
2009-08-06 2:52 ` Bryan Hsieh
2009-08-06 17:20 ` Mathieu Desnoyers
2009-08-06 17:24 ` Mathieu Desnoyers
2009-08-27 8:56 ` [ltt-dev] Change process name to be command line Bryan Hsieh
2009-08-27 10:31 ` Ajit R [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=458481.77854.qm@web63205.mail.re1.yahoo.com \
--to=ajitrzid@yahoo.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