Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Add thread info in 'struct step_over_info'
Date: Fri, 15 Apr 2016 13:29:00 -0000	[thread overview]
Message-ID: <1460726961-27486-1-git-send-email-yao.qi@linaro.org> (raw)

During the review https://sourceware.org/ml/gdb-patches/2016-04/msg00211.html,
we need to record the thread infor in step_over_info so that we know
the thread we are stepping over.  After I add thread info into
'struct step_over_info', I find other two fields in 'struct step_over_info'
become redundant, because 'aspace' and 'address' can be got from
'thread'.  On the hand, the step over info can be regarded as the
the thread we stepping over.

This patch series add a new field 'thread' and remove fields 'aspace' and
'address'.

Regression tested on x86_64-linux and aarch64-linux.

*** BLURB HERE ***

Yao Qi (2):
  Refactor function set_step_over_info
  Replace address and aspace with thread in struct step_over_info

 gdb/infrun.c | 50 ++++++++++++++++++++++++++------------------------
 1 file changed, 26 insertions(+), 24 deletions(-)

-- 
1.9.1


             reply	other threads:[~2016-04-15 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 13:29 Yao Qi [this message]
2016-04-15 13:29 ` [PATCH 1/2] Refactor function set_step_over_info Yao Qi
2016-04-15 13:29 ` [PATCH 2/2] Replace address and aspace with thread in struct step_over_info Yao Qi
2016-04-19 10:43   ` Pedro Alves
2016-04-19 13:55     ` Yao Qi
2016-04-20 18:01       ` Doug Evans
2016-04-20 18:03         ` Pedro Alves
2016-12-22 23:51           ` Doug Evans

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=1460726961-27486-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