Change py-thread-exited.exp to work with gdbserver

gdbserver does not notify gdb of new threads when they are created.
I'm not sure if this is documented anywhere, but it is mentioned on
this page:

https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity

Search for "Finding new threads in the inferior".

This behavior is a bit unfortunate -- I would think that it would be
better to arrange for such notification if something on the gdb side
is interested.

Meanwhile, this patch fixes py-thread-exited.exp to work around this
problem.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30677

1 files changed, 3 insertions, 3 deletions

diff --git a/gdb/testsuite/gdb.python/py-thread-exited.c b/gdb/testsuite/gdb.python/py-thread-exited.c
index fd0342b..d62133b 100644
--- a/gdb/testsuite/gdb.python/py-thread-exited.c
+++ b/gdb/testsuite/gdb.python/py-thread-exited.c
@@ -24,14 +24,14 @@ pthread_t thread3_id;
 
 void* do_thread (void* d)
 {
-  return NULL;
+  return NULL;			/* In thread */
 }
 
 int main (void)
 {
   pthread_create (&thread2_id, NULL, do_thread, NULL);
-  pthread_join (thread2_id, NULL);
   pthread_create (&thread3_id, NULL, do_thread, NULL);
+  pthread_join (thread2_id, NULL);
   pthread_join (thread3_id, NULL);
-  return 12;
+  return 12;			/* Done */
 }