Re: [PATCH] Add mi-threads-interrupt.exp test (PR 20039)

[Pedro Alves <palves@redhat.com>]

On 05/03/2016 10:57 PM, Pedro Alves wrote:
> I debugged this a little, and I see that the bug is that -exec-continue ends
> up with thread 3 selected, which generates a =thread-selected event.

Oh, BTW, I think this explains why reversing the thread list order exposed
this bug.  Before that patch, we'd issue an -exec-continue with
thread 1 selected, and gdb would resume thread 3, thread 2, and thread 1,
and thus end up with thread 1 selected again, and thus no =thread-selected
event would be output.  So I guess that if you select thread 2 before
the -exec-continue, the test exposes the bug even before the thread list
reordering patch.  Might be good to do that in the test in case that
detail ever changes again.

Thanks,
Pedro Alves