From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Fix gdb.threads/multiple-step-overs.exp fails on arm
Date: Thu, 29 Oct 2015 17:10:00 -0000 [thread overview]
Message-ID: <1446130862-12824-1-git-send-email-yao.qi@linaro.org> (raw)
Hi,
This patch series fixes fails in gdb.threads/multiple-step-overs.exp on
arm-linux. Patch 1 adds a new function, and patch 2 is the main part.
See details in patch 2.
Whole series is regression tested on x86_64-linux and arm-linux.
*** BLURB HERE ***
Yao Qi (2):
New function displaced_step_in_progress_thread
Fix gdb.threads/multiple-step-overs.exp fails on arm
gdb/infrun.c | 30 ++++++++++++++++++++++--------
1 file changed, 22 insertions(+), 8 deletions(-)
--
1.9.1
next reply other threads:[~2015-10-29 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 17:10 Yao Qi [this message]
2015-10-29 17:10 ` [PATCH 1/2] New function displaced_step_in_progress_thread Yao Qi
2015-11-04 17:20 ` Pedro Alves
2015-10-29 17:10 ` [PATCH 2/2] Fix gdb.threads/multiple-step-overs.exp fails on arm Yao Qi
2015-11-04 17:20 ` Pedro Alves
2015-11-09 11:24 ` Yao Qi
2015-11-17 12:33 ` Pedro Alves
2015-11-17 15:41 ` 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=1446130862-12824-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).