Getting thread names with thread_private

[Edgar Neubauer]

Greetings,

is there a method to dump the pthread thread names along with the thread local data for example with drcov? I want to use it to track which threads exactly access which code.

Regards.

[Derek Bruening]

There is no existing convenience routine.  If those are set on Linux with prctl(PR_SET_NAME then invoking SYS_prctl with PR_GET_NAME should be safe to run directly in a client context.  If that works out, please consider contributing a pull request to add a convenience API routine.

--
You received this message because you are subscribed to the Google Groups "DynamoRIO Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dynamorio-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dynamorio-users/d9ed854a-e8ac-4338-a5bc-812124e15566n%40googlegroups.com.

[Edgar Neubauer]

Hello,

thanks for your answer. The name is indeed set via prctl. I assume one should make the name part of per_thread_t ? Is this data structure created at a point where the calling thread is the one per_thread_t belongs to? I propose making the thread name part of the output file name. 

[Edgar Neubauer]

I see that the process id is already added to the filename. Can you tell me where this string is generated?

[Derek Bruening]

Yes, the thread init event is always run in the context of that thread (but the thread exit event does not have that guarantee).  Probably it uses drx_open_unique_appid_file() so searching for that should find it.

To view this discussion on the web visit https://groups.google.com/d/msgid/dynamorio-users/0e160745-5909-47ea-9430-74b07429e4e0n%40googlegroups.com.

[Edgar Neubauer]

Can I assume that every method that gets a valid drcontext is called by the thread this drcontext belongs to?

[Derek Bruening]

As mentioned, not in the thread exit event.

To view this discussion on the web visit https://groups.google.com/d/msgid/dynamorio-users/a6110fb2-38a7-4195-b988-fb62b827a0den%40googlegroups.com.