Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 7/8] fix py-finish-breakpoint.exp with always-async
Date: Tue, 30 Jul 2013 18:10:00 -0000	[thread overview]
Message-ID: <87r4efly0w.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20982.64444.939564.557857@ruffy.mtv.corp.google.com> (Doug	Evans's message of "Mon, 29 Jul 2013 16:33:16 -0700")

Doug> IOW, it'd be clearer if the patch did:
Doug>   int was_executing = target_has_execution;
Doug> and then augment the patch with whatever else is necessary
Doug> to make it correct.
Doug> [Assuming I understand correctly what the patch is trying to do.]

I think what is happening is that we need to detect the transition from
"not executing" to "executing a sync command".  But perhaps we don't
need to test sync_execution beforehand if we correctly detect execution.

Doug> Also, is target_has_execution what you want here?

Yeah, that is wrong.

Tom


  reply	other threads:[~2013-07-30 18:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 16:45 [PATCH 0/8] enable target-async by default Tom Tromey
2013-07-29 16:45 ` [PATCH 3/8] PR gdb/13860: make -interpreter-exec console "list" behave more like "list" Tom Tromey
2013-07-29 16:45 ` [PATCH 6/8] make dprintf.exp pass in always-async mode Tom Tromey
2013-07-29 16:45 ` [PATCH 2/8] add target method delegation Tom Tromey
2013-07-30 14:07   ` Metzger, Markus T
2013-07-30 14:47     ` Tom Tromey
2013-07-30 15:08       ` Metzger, Markus T
2013-07-30 15:13         ` Tom Tromey
2013-07-31 12:16         ` Agovic, Sanimir
2013-07-31 17:50           ` Tom Tromey
2013-07-29 16:45 ` [PATCH 5/8] PR gdb/13860: don't lose '-interpreter-exec console EXECUTION_COMMAND''s output in async mode Tom Tromey
2013-07-29 16:45 ` [PATCH 7/8] fix py-finish-breakpoint.exp with always-async Tom Tromey
2013-07-29 23:33   ` Doug Evans
2013-07-30 18:10     ` Tom Tromey [this message]
2013-07-30 20:56       ` Tom Tromey
2013-07-30  0:36   ` Yao Qi
2013-07-30 19:00     ` Tom Tromey
2013-07-29 16:45 ` [PATCH 8/8] enable target-async Tom Tromey
2013-07-29 18:30   ` Eli Zaretskii
2013-07-29 18:42     ` Tom Tromey
2013-07-29 16:45 ` [PATCH 4/8] PR gdb/13860: make "-exec-foo"'s MI output equal to "foo"'s MI output Tom Tromey
2013-07-29 16:45 ` [PATCH 1/8] fix latent bugs in ui-out.c Tom Tromey

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=87r4efly0w.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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