Re: [PATCH] Don't send queries to the MI interpreter

[Pedro Alves <palves@redhat.com>]

On 02/10/2017 07:02 PM, Simon Marchi wrote:
> On 17-02-10 12:44 PM, Pedro Alves wrote:
>> And it is at this point that I thought that it is odd to
>> query and ask for user input deep down inside the record layer,
>> while handling some asynchronous execution event -- i.e.,
>> deep down inside handle_inferior_event.  If we're buffering
>> output, when the user won't see the query anyway.
>> Hmm, now that I think of it, the "Do you want to auto delete
>> previous execution" query wouldn't be converted to an error,
>> but instead to a something like TARGET_WAITKIND_NO_HISTORY,
>> I suppose.
> 
> And TARGET_WAITKIND_NO_HISTORY would cause a user-visible stop?

Yes.  TARGET_WAITKIND_NO_HISTORY already exists.  It causes a
user-visible stop with "No more reverse-execution history".

This case is similar, except it's more like
"No more SPACE in reverse-execution history".

> (I'm processing the rest and will reply to your latest message)

Thanks,
Pedro Alves