Documenting Threads

I'm working on creating some platform documentation for a customer.
Part of this work involves identifiying all of the modules running in
the "baseline" system, including the threads that each module creates,
what priority they all run at, etc. Are there tools from MS or
third-parties that can help with this thread research process?

Thanks,
-Chris

Dean
Thu Dec 01 09:05:45 CST 2005

That kind of information is all available in from the Platform builder
debugger. You can see a list of all processes, the threads each creates,
their priorities etc.

That part is easy. What is not so easy is documenting the
purpose/functionality of each thread. I'm not sure if you need that info or
not. You could figure it out for the modules you have source for, but you'd
be out of luck for the remainder.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Chris Edgington" <cedgington@qualnetics.com> wrote in message
news:1133448139.524924.9770@o13g2000cwo.googlegroups.com...
> I'm working on creating some platform documentation for a customer.
> Part of this work involves identifiying all of the modules running in
> the "baseline" system, including the threads that each module creates,
> what priority they all run at, etc. Are there tools from MS or
> third-parties that can help with this thread research process?
>
> Thanks,
> -Chris
>

Valter
Thu Dec 01 09:10:25 CST 2005

"Chris Edgington" <cedgington@qualnetics.com> wrote in
news:1133448139.524924.9770@o13g2000cwo.googlegroups.com:

> I'm working on creating some platform documentation for a
> customer. Part of this work involves identifiying all of the
> modules running in the "baseline" system, including the threads
> that each module creates, what priority they all run at, etc. Are
> there tools from MS or third-parties that can help with this
> thread research process?
>

You may use kernel tracker to check the thread and processes running on
the system.
If you run it on a debug build it will give you some information about
the thread function names that could be useful to understand the
pourpouse of each thread.
Don't forget that thread can change its priority of the priority of
other threads at runtime and that could mean that the threads are not
grant to run always at the same priority level you read in kernel
tracker.

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)

Chris
Thu Dec 01 13:35:55 CST 2005

I realize that PB shows each process and its threads. But I need to
know what DLL each thread comes from. For example - DEVICE.EXE will
show a TON of threads - I want to pin each one to a specific driver
DLL. In the past - thats just been a manual process - thought I'd check
to see if there's a tool that can do it.

-Chris

Piet
Fri Dec 02 09:28:13 CST 2005

I don't think you can get that information from outside the thread. You
could log it from the threads, you would have make changes to all your
drivers of course.

Piet

Andrew
Sun Dec 04 21:06:00 CST 2005

I found you only get the thread function names in Kernel Tracker when
profiling is enabled - at least that's what I see in CE.NET 4.2 -
perhaps you get to see them with a normal debug image in CE 5.0?

In article <Xns971FA3C5F804EVALTERMINUTE@207.46.248.16>,
vminute@GoogleMAILservice.com says...
> ...
> You may use kernel tracker to check the thread and processes running on
> the system.
> If you run it on a debug build it will give you some information about
> the thread function names that could be useful to understand the

Steve
Mon Dec 05 08:23:49 CST 2005

No, that is true of all versions of CE. Kernel tracker logs the names only
when the symbol information is provided in the OS image in Profiling enabled
builds. (And ONLY for modules in the OS image. )

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com