Files
binutils-gdb/gdb/testsuite/gdb.python
Andrew Burgess a345d14fa6 gdb/testsuite: fix race condition in gdb.python/py-thread-exited.exp
I ran into a test failure on gdb.python/py-thread-exited.c.  The test
creates two threads and then catches the thread exits in Python.  The
test expects the threads to exit in a specific order.

As the test is currently written, it is _likely_, but not guaranteed,
that the threads will exit in the same order they are created, which
is what the test expects.

When running on a loaded system I ran into a case where the threads
exited in the reverse creation order, which caused the test to fail.

I could fix this by having the .exp file not care about the thread
order, or by changing the C file to force the order. I chose the
later, and added a pthread_barrier_t to ensure the threads exit in the
correct order.

There should be no change in what is tested after this commit.
2023-08-16 15:03:56 +01:00
..
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-05-23 10:09:28 -06:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-05-23 10:09:28 -06:00
2023-01-26 18:28:31 -07:00
2023-01-26 18:28:31 -07:00
2023-01-13 13:18:58 -07:00
2023-01-22 14:27:49 -07:00
2023-02-27 15:46:31 -07:00
2023-02-27 15:46:31 -07:00
2023-02-27 15:46:31 -07:00
2023-01-25 09:02:11 -07:00
2023-06-03 22:43:57 +02:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-06-19 17:13:05 +02:00
2023-01-13 13:18:58 -07:00
2023-06-12 12:09:39 -06:00
2023-06-03 22:43:57 +02:00
2023-06-03 22:43:57 +02:00
2023-01-13 13:18:58 -07:00