What to call a thread/cpu/?

[Andrew Cagney <ac131313 at cygnus dot com>]

Hello,

At present gdb has this thing called ``struct thread_info *''.  It
*should* contains several key GDB data structures including:

	o	debug state

		What GDB things it is doing
		to the thread - is it being
		stepped

	o	target state

		registers, memory, all that suff

(it doesn't but that is another story :-)

The thing to realise is that GDB can be used to debug not only threads
but also hardware CPUs.  Given that, the term ``thread'' is starting to
struggle and is showing signs of being very overloaded.

The question is, what internal name should GDB use when refering to a
thread/cpu/... or should it just stick to thread?

I've seen suggested/used:

	state
	context
	thread
	target
	inferior

You don't get to win a prise for comming up with the name but you do get
the chance to be able to show GDB to your grand children and say ``hey I
named that object'' :-)

	Andrew