Rename test.
authorPedro Alves <palves@redhat.com>
Fri, 21 Feb 2014 13:30:12 +0000 (13:30 +0000)
committerPedro Alves <palves@redhat.com>
Fri, 21 Feb 2014 13:30:12 +0000 (13:30 +0000)
commitea4758f2dd33c0081abc89b011c4755453af9efc
tree4dde2ca7243c074e6135077ed63a16f66c9854bc
parent0cbc458c9fde560ad369d197ed90b94452cc3b06
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.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.c [new file with mode: 0644]
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp [new file with mode: 0644]
gdb/testsuite/gdb.threads/step-after-sr-lock.c [deleted file]
gdb/testsuite/gdb.threads/step-after-sr-lock.exp [deleted file]