[RFA/doco] Document task-specific breakpoints
Joel Brobecker
brobecker@adacore.com
Thu Mar 26 22:50:00 GMT 2009
Hello Eli,
> > +Breakpoint 5, test_task_debug.tB.1 (_task=0x11ffffc60)
> ^^^^^
> What is this part? Should we explain it in some footnote? And what
> about _task=0x11ffffc60 part, should it perhaps be explained, too?
Hmm, good point. These are actually old compiler artifacts that we
got rid of since writing that documentation. The original testcase
was using what we call a task "entry" I believe, which is the reason
for the "_task" parameter. We could just as well have used a function
so I cleaned up the example to make it simpler.
> > +(@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.
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.
Thanks,
--
Joel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: task-doc.diff
Type: text/x-diff
Size: 2853 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20090326/7859b239/attachment.bin>
More information about the Gdb-patches
mailing list