Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Don't send queries to the MI interpreter
Date: Fri, 10 Feb 2017 19:03:00 -0000	[thread overview]
Message-ID: <cbc68b64-b5e6-4aba-fdfc-8b77fef535f8@ericsson.com> (raw)
In-Reply-To: <85ae4ad9-acdc-c9ba-6606-a7ac2abc7e2e@redhat.com>

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?

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


  parent reply	other threads:[~2017-02-10 19:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 16:37 Simon Marchi
2017-02-10 16:48 ` Pedro Alves
2017-02-10 16:52   ` Simon Marchi
2017-02-10 17:12     ` Pedro Alves
2017-02-10 17:44       ` Pedro Alves
2017-02-10 18:07         ` Pedro Alves
2017-02-10 18:36           ` Pedro Alves
2017-02-10 19:08             ` Simon Marchi
2017-02-10 19:23               ` Pedro Alves
2017-02-10 19:06           ` Simon Marchi
2017-02-10 19:20             ` Pedro Alves
2017-02-10 19:26               ` Simon Marchi
2017-02-10 19:32                 ` Pedro Alves
2017-02-10 19:30             ` Pedro Alves
2017-02-10 19:03         ` Simon Marchi [this message]
2017-02-10 19:08           ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cbc68b64-b5e6-4aba-fdfc-8b77fef535f8@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox