Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Flip the interpreter to synchronously wait for commands finishing, in command lists and similars
Date: Sat, 03 Sep 2011 09:21:00 -0000	[thread overview]
Message-ID: <CACTLOFp0P5YES54J1GkJMVHxeTCO7hJqzTgDpujQWGvFd_okCQ@mail.gmail.com> (raw)
In-Reply-To: <201109021807.41992.pedro@codesourcery.com>

On Fri, Sep 2, 2011 at 10:07 AM, Pedro Alves <pedro@codesourcery.com> wrote:
>
> With this patch, synchronous execution commands (the regular step, next,
> etc., that is, those with an & suffixed) with a target running
> in async mode work correctly (AFAICT) with all current use cases.    We
> can consider flipping on async on by default, and then incrementally
> convert specific paths to state machines, for new use cases, rather than
> delaying flipping on async on by default until _everything_ is converted
> into a state-machine.

I was hoping this might fix, (but doesn't seem to) the following case:

./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue'
./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue&'

both these commands exhibit:
Continuing.

Program received signal SIGSTOP, Stopped (signal).
.....
(gdb)

thus changing the behavior of '-ex continue' should we turn
target-async on by default.


  reply	other threads:[~2011-09-02 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 17:22 Pedro Alves
2011-09-03  9:21 ` Matt Rice [this message]
2011-09-05 14:48   ` 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=CACTLOFp0P5YES54J1GkJMVHxeTCO7hJqzTgDpujQWGvFd_okCQ@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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