aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-symtab.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2019-10-14 00:37:30 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2019-10-14 12:12:24 -0400
commit9223170f68f85787b9cd85e76d3bac3eaa69cafb (patch)
tree701269c506c632fb511b9e136ef4e81688e1f757 /gdb/python/py-symtab.c
parent6acc1a0b9d3dd16741474891eddbf77415cd70b1 (diff)
downloadgdb-9223170f68f85787b9cd85e76d3bac3eaa69cafb.zip
gdb-9223170f68f85787b9cd85e76d3bac3eaa69cafb.tar.gz
gdb-9223170f68f85787b9cd85e76d3bac3eaa69cafb.tar.bz2
gdb.mi/list-thread-groups-available.exp: read entries one by one instead of increasing timeout
Commit 580f1034 ("Increase timeout in gdb.mi/list-thread-groups-available.exp") changed gdb.mi/list-thread-groups-available.exp to significantly increase the timeout, which was necessary for when running with make check-read1. Pedro suggested a better alternative, which is to use gdb_test_multiple and consume one entry at a time. This patch does that. gdb/testsuite/ChangeLog: * gdb.mi/list-thread-groups-available.exp: Read entries one by one instead of increasing timeout. Change-Id: I51b689458503240f24e401f054e6583d9172ebdf
Diffstat (limited to 'gdb/python/py-symtab.c')
0 files changed, 0 insertions, 0 deletions