aboutsummaryrefslogtreecommitdiff
path: root/gdb/aix-thread.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2017-03-13 18:02:07 -0400
committerSimon Marchi <simon.marchi@ericsson.com>2017-03-13 18:02:07 -0400
commit896c0c1edee117ea333c66b1adac8c6f4def3f2b (patch)
tree5c7888fd7d77f65038ad0007e606f8e2cf0b6686 /gdb/aix-thread.c
parentb9da89d161e3903faa335f444af2bf05e40f926e (diff)
downloadbinutils-896c0c1edee117ea333c66b1adac8c6f4def3f2b.zip
binutils-896c0c1edee117ea333c66b1adac8c6f4def3f2b.tar.gz
binutils-896c0c1edee117ea333c66b1adac8c6f4def3f2b.tar.bz2
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.
Diffstat (limited to 'gdb/aix-thread.c')
0 files changed, 0 insertions, 0 deletions