public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com
Subject: [PATCH 0/2] Context-switch in finish-step-over flow
Date: Mon, 20 Apr 2020 18:24:41 +0200	[thread overview]
Message-ID: <cover.1587399322.git.tankut.baris.aktemur@intel.com> (raw)

Hi,

While addressing Pedro's comments to a patch about 'stop_all_threads' at

  https://sourceware.org/pipermail/gdb-patches/2020-April/167664.html

the need for this two-part series arose.  This small series will act as
as a predecessor to the next revision of the patch linked above.

Regards.
Baris


Tankut Baris Aktemur (2):
  testsuite: introduce 'default_gdb_start_post_cmd' as an overridable
    function
  gdb/infrun: switch the context before 'displaced_step_restore'

 gdb/infrun.c                                  | 11 +++--
 gdb/testsuite/gdb.multi/run-only-second-inf.c | 22 +++++++++
 .../gdb.multi/run-only-second-inf.exp         | 49 +++++++++++++++++++
 gdb/testsuite/lib/gdb.exp                     | 12 +++++
 4 files changed, 89 insertions(+), 5 deletions(-)
 create mode 100644 gdb/testsuite/gdb.multi/run-only-second-inf.c
 create mode 100644 gdb/testsuite/gdb.multi/run-only-second-inf.exp

-- 
2.17.1


             reply	other threads:[~2020-04-20 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 16:24 Tankut Baris Aktemur [this message]
2020-04-20 16:24 ` [PATCH 1/2] testsuite: introduce 'default_gdb_start_post_cmd' as an overridable function Tankut Baris Aktemur
2020-04-20 16:24 ` [PATCH 2/2] gdb/infrun: switch the context before 'displaced_step_restore' Tankut Baris Aktemur
2020-04-21 14:38   ` Pedro Alves
2020-04-21 15:29     ` Aktemur, Tankut Baris

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=cover.1587399322.git.tankut.baris.aktemur@intel.com \
    --to=tankut.baris.aktemur@intel.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).