Re: Extra Thread Info

[jtc at redback dot com (J.T. Conklin)]

>>>>> "Jonathan" == Jonathan Larmour <jlarmour@cygnus.co.uk> writes:
Jonathan> I think what is required is to draw up a list of all the
Jonathan> thread concepts we already know that users would want to
Jonathan> know about: thread ID, name, priority, state, stack frame at
Jonathan> least. A target stub may support any or all of these.

The problem is that this is an open ended set of variables, and they
are represented with different types in different OSs.  For example,
to debug problems at different times I've had to look at thread ID,
name, priority, inherited priority, state, stack bounds (stack top &
bottom, and current stack pointer), number of ticks since task was
last scheduled, number of interrupts received while in this task's
context, number of times task has be placed on run queue, number of
times task has been preemted, number of times task has yielded
unconditionally, etc., etc., etc.  And that's just my list.  Combine
that with everyone elses, and it gets out of hand...

        --jtc

-- 
J.T. Conklin
RedBack Networks