From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove setup_kfail server/13796 in disp-step-syscall.exp
Date: Thu, 18 Feb 2016 12:06:00 -0000 [thread overview]
Message-ID: <56C5B3DE.9040601@redhat.com> (raw)
In-Reply-To: <1455796823-18128-1-git-send-email-yao.qi@linaro.org>
On 02/18/2016 12:00 PM, Yao Qi wrote:
> This patch series add fork support in target remote,
>
> [PATCH v2 0/3] Target remote mode fork and exec support
> https://sourceware.org/ml/gdb-patches/2015-12/msg00144.html
>
> so GDB can be informed about the child, and adjust child correctly in
> displaced stepping. The PR server/13796 was fixed by this patch
> series actually. Test results on buildbot show this KFAIL->KPASS
> change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html
>
> gdb/testsuite:
>
> 2016-02-18 Yao Qi <yao.qi@linaro.org>
>
> * gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
> Don't call setup_kfail.
OK.
Thanks,
Pedro Alves
prev parent reply other threads:[~2016-02-18 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:00 Yao Qi
2016-02-18 12:06 ` Pedro Alves [this message]
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=56C5B3DE.9040601@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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).