This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH][gdb/testsuite] Fix target_supports_scheduler_locking raciness
- From: Pedro Alves <palves at redhat dot com>
- To: Tom de Vries <tdevries at suse dot de>, gdb-patches at sourceware dot org
- Date: Tue, 9 Oct 2018 13:58:26 +0100
- Subject: Re: [PATCH][gdb/testsuite] Fix target_supports_scheduler_locking raciness
- References: <20181004174015.GA20307@delia>
On 10/04/2018 06:40 PM, Tom de Vries wrote:
> Hi,
>
> 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.
>
> OK for trunk?
The fix itself it OK. Thanks for doing that. Can you please
submit the gdb-caching-proc.exp separately, with its own rationale?
Thanks,
Pedro Alves