Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 7/8] fix py-finish-breakpoint.exp with always-async
Date: Tue, 30 Jul 2013 00:36:00 -0000	[thread overview]
Message-ID: <51F70A63.5090909@codesourcery.com> (raw)
In-Reply-To: <1375116324-32092-8-git-send-email-tromey@redhat.com>

On 07/30/2013 12:45 AM, Tom Tromey wrote:
> However, the code did not follow this comment -- it didn't check to
> see if the command started the target.
>
> This patch fixes the problem by noting whether the target was
> executing in sync_execution mode before running the command, and then
> augmenting the condition to test this as well.

The rationale looks right to me.

>
> Built and regtested on x86-64 Fedora 18.
>
> 	* top.c (execute_command): Only dispatch events if command
> 	started target.

I opened PR 14135 for an internal error we saw in 
gdb.python/py-finish-breakpoint.exp when async is on.  If it is the 
error this patch is to fix, please mention this patch fixes PR 14135 in 
ChangeLog.

http://sourceware.org/bugzilla/show_bug.cgi?id=14135

I also posted a patch for this PR, but it doesn't apply to current trunk.

-- 
Yao (齐尧)


  parent reply	other threads:[~2013-07-30  0:36 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 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 1/8] fix latent bugs in ui-out.c 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 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 6/8] make dprintf.exp pass in always-async mode 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 3/8] PR gdb/13860: make -interpreter-exec console "list" behave more like "list" 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
2013-07-30 20:56       ` Tom Tromey
2013-07-30  0:36   ` Yao Qi [this message]
2013-07-30 19:00     ` 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=51F70A63.5090909@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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