[lkml]   [2009]   [Aug]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Tracing thread name
Hi Mathieu,

Mathieu Desnoyers a écrit :
> * Matthieu CASTET ( 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-08-04 12:15    [W:0.346 / U:3.548 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site