Thanks for the answer it works or at least I got more precision than a simple "BinderThread #"
On 27 jan, 02:38, rong <rong1...@gmail.com> wrote: > What you really need is to get the thread group leader pid by using > > task_tgid_vnr(current) > > and use that pid in whatever name lookup function you have. If you > still can't get sensible thing, you probably want to have a look at > proc_pid_cmdline() function in fs/proc/base.c to see how it copies the > argument buffer from another process's vm. > > Regards, > > Rong > > On Jan 27, 10:20 am, andria <andri...@gmail.com> wrote: > > > > > > > > > Hi, > > > I added some "printk" in order to know what are the processes using > > binder_thread_read function. The output result contains a lot of > > processes named BinderThread. But what I really wanted to know is the > > process / appli inside of which the BinderThread is running. As far as > > I know a thread pool is maintained in every processes or at least the > > processes running service providing remote calls. > > > I thought maybe I should look for the name of the parents of the > > thread but it turned out that their parents are zygote or init. > > > Can anyone help me? > > > Thanks. > > > Andria -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
