You do need to be careful when reading various fora (and even some textbooks), though, as the confusion between "process" and "thread" runs deep. Further confusing things is the fact that sometimes a "process" is referred to as a "task", while in other cases "task" refers to a "thread". (Depends on the traditions of the system in question and the particulars of how Java is implemented.) And of course there's then the JVM (or DVM) -- is there a 1-1 correspondence between JVM and process or can a process host more than one JVM?? It all depends.
In general you should think in terms of the JVM/DVM instead of the process, and when using the term "thread" always mean "Java thread" (which may be different from other forms of thread the system supports). By sticking with these concepts you're isolated from a lot of system dependencies, even if you stray outside of the Android environment. (Though I don't offhand know of a way to access some sort of JVM/DVM id.) On Sep 22, 11:39 am, john brown <[email protected]> wrote: > Hello, > > I am trying to understand threads and how they work, and when, etc. I > expected the pid in LogCat to be different in the background thread > logs but the pid is always the same. > > Is the pid something other than the thread ID? If it is, is there a > way to indicate the thread ID in LogCat? > > Thanks, John Brown -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
