This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA/doco] Document task-specific breakpoints
> Date: Fri, 27 Mar 2009 09:10:51 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> The problem is that I don't understand what it is that is so confusing
> to you.
What is confusing is this:
(@value{GDBP}) info tasks
ID TID P-ID Pri State Name
1 140022020 0 15 Child Activation Wait main_task
2 140045060 1 15 Accept/Select Wait t2
3 140044840 1 15 Runnable t1
* 4 140056040 1 15 Running t3
Task 2 is running, okay.
(@value{GDBP}) b 15 task 2
Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.
Set a breakpoint for task 2.
Breakpoint 5, test_task_debug () at test_task_debug.adb:15
Breakpoint is hit by task 2.
(@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
3 140044840 1 15 Runnable t1
4 140056040 1 15 Delay Sleep t3
And task 2 is still running, even though it has hit the breakpoint.
Did I succeed in explaining what is confusing? The task was running,
then it hit the breakpoint, but it is still "running".
If this is normal, at least remove the second "info tasks" and its
output from the example.