Rename test.

I realized that the name of this test only made sense when considering
the old (never committed) implementation of the fix that came along
with the test originally, that forced a schedlock while a step-resume
(to get over the signal handler) was inserted.  The final solution
that went into the tree does not force that locking.

So this renames it to something more descriptive.

gdb/testsuite/
2014-02-21  Pedro Alves  <palves@redhat.com>

	* gdb.threads/step-after-sr-lock.c: Rename to ...
	* gdb.threads/signal-while-stepping-over-bp-other-thread.c: ... this.
	* gdb.threads/step-after-sr-lock.exp: Rename to ...
	* gdb.threads/signal-while-stepping-over-bp-other-thread.exp:
	... this.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index d7e86106c4af6a8186e62fdc792121f1ff15752a..9b409cb268469c0c4614e69a577e8731b5198ce8 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2014-02-21  Pedro Alves  <palves@redhat.com>
+
+       * gdb.threads/step-after-sr-lock.c: Rename to ...
+       * gdb.threads/signal-while-stepping-over-bp-other-thread.c: ... this.
+       * gdb.threads/step-after-sr-lock.exp: Rename to ...
+       * gdb.threads/signal-while-stepping-over-bp-other-thread.exp:
+       ... this.
+
 2014-02-20  Sergio Durigan Junior  <sergiodj@redhat.com>
 
        PR tdep/16397

diff --git a/gdb/testsuite/gdb.threads/step-after-sr-lock.c b/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.c
similarity index 100%
rename from gdb/testsuite/gdb.threads/step-after-sr-lock.c
rename to gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.c

diff --git a/gdb/testsuite/gdb.threads/step-after-sr-lock.exp b/gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
similarity index 100%
rename from gdb/testsuite/gdb.threads/step-after-sr-lock.exp
rename to gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp