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>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/7] Merge async and sync code paths some more
Date: Wed, 12 Aug 2015 19:48:00 -0000	[thread overview]
Message-ID: <55CBA30E.9090004@ericsson.com> (raw)
In-Reply-To: <1439398917-22761-2-git-send-email-palves@redhat.com>

On 15-08-12 01:01 PM, Pedro Alves wrote:
> diff --git a/gdb/mi/mi-interp.c b/gdb/mi/mi-interp.c
> index 99ce385..bdd8e21 100644
> --- a/gdb/mi/mi-interp.c
> +++ b/gdb/mi/mi-interp.c
> @@ -309,16 +309,8 @@ mi_execute_command_wrapper (const char *cmd)
>  static void
>  mi_on_sync_execution_done (void)
>  {
> -  /* MI generally prints a prompt after a command, indicating it's
> -     ready for further input.  However, due to an historical wart, if
> -     MI async, and a (CLI) synchronous command was issued, then we
> -     will print the prompt right after printing "^running", even if we
> -     cannot actually accept any input until the target stops.  See
> -     mi_on_resume.  However, if the target is async but MI is sync,
> -     then we need to output the MI prompt now, to replicate gdb's
> -     behavior when neither the target nor MI are async.  (Note this
> -     observer is only called by the asynchronous target event handling
> -     code.)  */
> +  /* If we MI is sync, then output the MI prompt now, indicating we're
> +     ready for further input.  */

"If we MI is sync"


  reply	other threads:[~2015-08-12 19:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 17:02 [PATCH 0/7] Replace continuations with an extendable "class" Pedro Alves
2015-08-12 17:02 ` [PATCH 2/7] Replace "struct continuation" mechanism by something more extensible Pedro Alves
2015-08-18 12:50   ` Yao Qi
2015-08-19 14:55     ` Pedro Alves
2015-08-12 17:02 ` [PATCH 3/7] Convert infcalls to thread_fsm mechanism Pedro Alves
2015-08-12 17:02 ` [PATCH 4/7] Convert the until/advance commands " Pedro Alves
2015-08-12 17:02 ` [PATCH 1/7] Merge async and sync code paths some more Pedro Alves
2015-08-12 19:48   ` Simon Marchi [this message]
2015-08-17 17:54     ` Pedro Alves
2015-08-17 19:28       ` Simon Marchi
2015-08-18 10:48   ` Yao Qi
2015-08-19 14:11     ` Pedro Alves
2015-08-27 13:26       ` Yao Qi
2015-10-16  0:35   ` Joel Brobecker
2015-10-16 12:24     ` Pedro Alves
2015-10-16 16:22       ` Joel Brobecker
2015-10-16 16:37         ` Pedro Alves
2015-10-16 17:05           ` Joel Brobecker
2015-10-22 16:18             ` Pedro Alves
2015-08-12 17:11 ` [PATCH 7/7] Delete enum inferior_event_handler::INF_TIMER Pedro Alves
2015-08-18 11:22   ` Yao Qi
2015-08-12 17:11 ` [PATCH 5/7] Garbage collect dummy_frame_ctx_saver Pedro Alves
2015-08-12 17:11 ` [PATCH 6/7] Garbage collect thread continuations Pedro Alves
2015-08-18 12:52 ` [PATCH 0/7] Replace continuations with an extendable "class" Yao Qi
2015-08-19 14:56   ` Pedro Alves
2015-09-09 17:33   ` 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=55CBA30E.9090004@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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