This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA/doco] Document task-specific breakpoints
> > > > +(@value{GDBP}) info tasks
> > > > + ID TID P-ID Pri State Name
> > > > + 1 140022020 0 15 Child Activation Wait main_task
> > > > +* 2 140045060 1 15 Running t2
> > >
> > > "Running"? shouldn't it be stopped at breakpoint?
> >
> > In practice, yes, it is stopped. But this information is printed
> > from the point of view of the runtime. To the runtime, task "t2"
> > is running.
>
> Sorry, I don't understand. Can you elaborate?
Sure. These states indicate what the tasks are currently doing.
For instance "Child activation wait" above means that the task
is waiting for its children to complete before it terminates
(see the description of these state in the Manual). "Running"
is another one of these states which just says that, from the
point of view of the program, that this task is not waiting
for an event, nor sleeping, nor waiting for a rendez-vous, etc.
It's simply executing some code.
> > Attached is a new version of the documentation patch:
> >
> > * gdb.texinfo (Ada Tasks): Add documentation about task-specific
> > breakpoints.
> > (Set Breaks): Add reference to thread-specific and task-specific
> > breakpoints.
>
> OK, but I think the "running" part should be either fixed or
> explained.
I think that "Running" is fine and doesn't need fixing. So let me know
if you'd like me to explain further.
--
Joel