OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Pedro Alves 2014-02-21 13:30:12 +00:00
parent 0cbc458c9f
commit ea4758f2dd
3 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
gdb/testsuite/ChangeLog
View File

@ -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

0
gdb/testsuite/gdb.threads/step-after-sr-lock.c → gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.c
View File

0
gdb/testsuite/gdb.threads/step-after-sr-lock.exp → gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp
View File