This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: What to call a thread/cpu/?
Andrew Cagney <ac131313@cygnus.com> writes:
> Daniel Berlin wrote:
> >
> > Andrew Cagney <ac131313@cygnus.com> writes:
> >
> > > 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
> >
> > Just a note, this isn't necessarily correct.
> > Not all operating systems let you get at the thread registers all the
> > time. The thread must be stopped, not in the kernel, etc.
>
> I should have said a context's target state. Each context has a
> separate target state.
> See other e-mail.
Yup.
>
> > What you really want to do is replace target_ops with something like
> > a thread_ops, associate the architecture with the thread
>
> See my other e-mail.
That'll teach me to read in chronological order.
:)
>
> Andrew