Re: [PATCH] Have SIGTERM promptly quit GDB even when the dummy target is active

[Patrick Palka <patrick@parcs.ath.cx>]

On Mon, Jul 27, 2015 at 10:53 AM, Pedro Alves <palves@redhat.com> wrote:
> On 07/24/2015 07:33 PM, Patrick Palka wrote:
>
>> gdb/ChangeLog:
>>
>>       * event-top.c (handle_sigterm): Don't inspect
>>       target_can_async_p.  Always set the quit flag and always mark
>>       the async signal handler.
>
> OK.
>
>> +gdb_start
>> +
>> +set gdb_pid [exp_pid -i [board_info host fileid]]
>> +remote_exec host "kill -TERM $gdb_pid"
>> +
>> +set test "expect eof"
>> +
>> +gdb_expect 5 {
>
> Any reason not to use gdb_test_multiple, like:
>
>  gdb_test_multiple "" $test {
>    -timeout 5
>    eof {
>       pass $test
>    }
>  }
>
> ?

No reason.  I'll change the test to use gdb_test_multiple and commit the patch.