On Sun, Feb 11, 2018 at 4:42 AM, Samuel Thibault <samuel.thiba...@gnu.org>
wrote:
> Brent W. Baccala, on dim. 11 févr. 2018 01:23:10 -0500, wrote:
> > So how can I figure out where in processor_set_tasks() (or its
> subroutines)
> > that the kernel has blocked?
>
> show all tasks
>
> Should give you the list of tasks, then
>
> show task $task123
>
> shows the list of threads, then
>
> trace/t $task123.4
>
> shows the backtrace of the thread.
Thank you, Samuel.
I had another problem, though - gdb was attached to the program and it was
halted. That caused a lot of my threads to report their traces as
"Continuation thread_bootstrap_return". I had to detach gdb, or at least
"continue" the program, before the thread backtraces reported normally. I
thought I was doing something wrong with the debugger.
So, there was nothing blocked in processor_set_tasks(); I was just confused.
Thanks again for your helpful reply.
agape
brent
