From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Fix PR14135
Date: Fri, 25 May 2012 09:56:00 -0000 [thread overview]
Message-ID: <1337939766-1579-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
This patch series is to fix PR14135, some python test fails in
async mode. Patch 1/3 is a new test case for PR12929, which
will be used to prove my later changes are correct.
Patch 2/3 and 3/3 are to fix PR14135.
Regression tested on x86_64-linux {native,gdbserver} x {sync, async}.
P.S. I knew Pedro is looking at this issue as well, but I don't
want the patch series `run all-stop on top of non-stop target'
pending there indefinitely, so I have a try to fix these
async-related bugs.
next reply other threads:[~2012-05-25 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 9:56 Yao Qi [this message]
2012-05-25 9:56 ` [PATCH 1/3] New test case for PR12929 Yao Qi
2013-07-30 19:49 ` Tom Tromey
2013-07-30 20:11 ` Tom Tromey
2013-07-31 7:53 ` Yao Qi
2013-07-31 15:19 ` Tom Tromey
2013-08-01 6:39 ` Yao Qi
2012-05-25 9:56 ` [PATCH 3/3] Match output in async mode Yao Qi
2013-07-30 20:06 ` Tom Tromey
2013-07-31 7:45 ` Yao Qi
2012-05-25 9:56 ` [PATCH 2/3] Don't force interpreter sync mode in execute_gdb_command Yao Qi
2013-07-30 19:55 ` Tom Tromey
2013-07-30 20:13 ` Tom Tromey
2012-07-17 2:51 ` Fix PR14135 Yao Qi
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=1337939766-1579-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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