component names in ps or htop

Submitted by dustingooding on Fri, 2013-04-26 15:20

Is there a way to get component names (or some other identifier) in ps/htop to see what system resources each component is taking? Currently, all I see are a handful of "rttlua-gnulinux -i someFile.lua" entries.

I'm assuming this capability exists, and I just can't find it in the documentation?

--
Dustin Gooding
NASA/JSC Robotics

‹ Marshalling for a service Some advances in Rock and plain-RTT components ›
»

component names in ps or htop

Submitted by Polch on Fri, 2013-04-26 17:40.

On 04/26/2013 05:20 PM, Gooding, Dustin R. (JSC-ER411) wrote:
> Is there a way to get component names (or some other identifier) in ps/htop to see what system resources each component is taking? Currently, all I see are a handful of "rttlua-gnulinux -i someFile.lua" entries.
>
> I'm assuming this capability exists, and I just can't find it in the documentation?
>
> --
> Dustin Gooding
> NASA/JSC Robotics
>
>
>
>

I've submitted patches in order to get activities/task names : http://bugs.orocos.org/show_bug.cgi?id=1016

The patch uses pthread_setname_np (instead of the more standard prctl PR_SET_NAME that lacks the availability to specify thread id).

So you are able to do top -H -p <pid>

Feel free to test the patch.

However, the mapping between the taskname and the activity name isn't always straight forward (one activity for several tasks for instance).

Regards.

--
Paul Chavent
ONERA/DCSD

»

Re:

Submitted by Tim on Mon, 2013-05-06 12:02.
>Gooding, Dustin R. (JSC-ER411) wrote: >> Is there a way to get component names (or some other identifier) in ps/htop to see what >system resources each component is taking? Currently, all I see are a handful of "rttlua->gnulinux -i someFile.lua" entries. >> >> I'm assuming this capability exists, and I just can't find it in the documentation? >> >> -- >> Dustin Gooding >> NASA/JSC Robotics >> >> >> >> >>I've submitted patches in order to get activities/task names : >http://bugs.orocos.org/show_bug.cgi?id=1016 >>The patch uses pthread_setname_np (instead of the more standard prctl PR_SET_NAME that >lacks the availability to specify thread id). >>So you are able to do top -H -p <pid> >>Feel free to test the patch. >

Hi Paul, we are trying to test the patch. However after applying the patch what is the next step? How do we actually set a name for a component?

>However, the mapping between the taskname and the activity name isn't always straight >forward (one activity for several tasks for instance). >>Regards. >

>-- >Paul Chavent >ONERA/DCSD

Regards,

Tim

»