]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit - gdb/testsuite/ChangeLog
testsuite: Introduce dejagnu_version
authorSimon Marchi <simon.marchi@ericsson.com>
Mon, 13 Mar 2017 22:02:07 +0000 (18:02 -0400)
committerSimon Marchi <simon.marchi@ericsson.com>
Mon, 13 Mar 2017 22:02:07 +0000 (18:02 -0400)
commit896c0c1edee117ea333c66b1adac8c6f4def3f2b
tree5c7888fd7d77f65038ad0007e606f8e2cf0b6686
parentb9da89d161e3903faa335f444af2bf05e40f926e
testsuite: Introduce dejagnu_version

The next patch will require checking the DejaGnu version.  There is
already a test that does this,
gdb.threads/attach-many-short-lived-threads.exp.  This patch introduces
a new procedure, dejagnu_version, and makes that test use it.

The version number is "right-padded" with zeroes, to make sure that we
always return a triplet (major, minor, patch).

The procedure does not consider the DejaGnu versions from git.  For
example, if you used DejaGnu from its current master branch, the version
would be "1.6.1-git", meaning that 1.6.1 will be the next release.  I
figured we'll cross that bridge when (and if) we get there.

gdb/testsuite/ChangeLog:

* lib/gdb.exp (dejagnu_version): New proc.
* gdb.threads/attach-many-short-lived-threads.exp (bad_dejagnu):
Use dejagnu_version.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp
gdb/testsuite/lib/gdb.exp