From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Honour software single step in fallback of displaced stepping
Date: Thu, 16 Apr 2015 12:00:00 -0000 [thread overview]
Message-ID: <552FA447.3060804@gmail.com> (raw)
In-Reply-To: <86iod7vtgg.fsf@gmail.com>
On 08/04/15 10:51, Yao Qi wrote:
>> I don't mind if you push your patch in first. I'll just
>> >end up deleting that code again when I rebase it.
> I'll let your patches go in.
Hi Pedro,
Since this bug is still in FSF trunk, most of the tests in
gdb.threads/non-stop-fair-events.exp are timeout on arm-linux,
and takes much more time to run the whole testsuite.
Can I push patch 1/2 in to fix this problem? assuming
your V3 "all stop on top of non-stop" series can't go in in a
a couple of days.
--
Yao (é½å°§)
next prev parent reply other threads:[~2015-04-16 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 15:52 Yao Qi
2015-04-07 15:52 ` [PATCH 2/2] " Yao Qi
2015-04-07 15:52 ` [PATCH 1/2] [gdbserver] assert on step if !can_hardware_single_step Yao Qi
2015-04-07 17:09 ` Pedro Alves
2015-04-07 16:59 ` [PATCH 0/2] Honour software single step in fallback of displaced stepping Pedro Alves
2015-04-08 9:51 ` Yao Qi
2015-04-16 12:00 ` Yao Qi [this message]
2015-04-16 12:02 ` Pedro Alves
2015-04-16 13:01 ` 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=552FA447.3060804@gmail.com \
--to=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).