[binutils-gdb] [gdb/testsuite] Fix target_supports_scheduler_locking raciness
sergiodj+buildbot@sergiodj.net
sergiodj+buildbot@sergiodj.net
Tue Oct 9 14:06:00 GMT 2018
*** TEST RESULTS FOR COMMIT 58bbcd02dee8ba018b97706c068ed8ed7afac15d ***
Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 58bbcd02dee8ba018b97706c068ed8ed7afac15d
[gdb/testsuite] Fix target_supports_scheduler_locking raciness
When calling gdb_start_cmd, it's the caller's responsibility to wait for gdb
to return to the prompt. In target_supports_scheduler_locking, that's not the
case, and consequently, target_supports_scheduler_locking fails spuriously.
Fix by using runto_main instead.
Build and reg-tested on x86_64-linux.
2018-10-09 Tom de Vries <tdevries@suse.de>
* lib/gdb.exp (target_supports_scheduler_locking): Replace gdb_start_cmd
with runto_main.
More information about the Gdb-testers
mailing list