Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Omair Javaid <omair.javaid@linaro.org>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com,	prudo@linux.ibm.com,	arnez@linux.vnet.ibm.com,
	peter.griffin@linaro.org,	Ulrich.Weigand@de.ibm.com,
	kieran@linuxembedded.co.uk
Subject: [RFC PATCH 3/6] Add scoped_restore_regcache_ptid
Date: Tue, 29 Jan 2019 05:03:00 -0000	[thread overview]
Message-ID: <1548738199-9403-4-git-send-email-omair.javaid@linaro.org> (raw)
In-Reply-To: <1548738199-9403-1-git-send-email-omair.javaid@linaro.org>

From: Philipp Rudo <prudo@linux.ibm.com>

When a target and its target beneath use different ptids to identify a
thread the regcaches ptid has to be set/restored when calls are passed down
to the target beneath to e.g. fetch_registers.  Add a scoped_restore to
simplify this.

gdb/ChangeLog:

	regcache.h (scoped_restore_regcache_ptid): New class.
---
 gdb/regcache.h | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/gdb/regcache.h b/gdb/regcache.h
index 2b703ea..389d220 100644
--- a/gdb/regcache.h
+++ b/gdb/regcache.h
@@ -429,6 +429,27 @@ private:
   registers_changed_ptid (ptid_t ptid);
 };
 
+/* Save/restore the current ptid of REGCACHE.  */
+
+class scoped_restore_regcache_ptid
+{
+public:
+  scoped_restore_regcache_ptid (regcache *regcache)
+    : m_regcache (regcache), m_ptid (regcache->ptid ())
+  {}
+
+  ~scoped_restore_regcache_ptid ()
+    {
+      m_regcache->set_ptid (m_ptid);
+    }
+
+  DISABLE_COPY_AND_ASSIGN (scoped_restore_regcache_ptid);
+
+private:
+  regcache *m_regcache;
+  ptid_t m_ptid;
+};
+
 class readonly_detached_regcache : public readable_regcache
 {
 public:
-- 
2.7.4


  parent reply	other threads:[~2019-01-29  5:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  5:03 [RFC PATCH 0/6] Support for Linux kernel thread aware debug Omair Javaid
2019-01-29  5:03 ` [RFC PATCH 2/6] Add libiberty/concat styled concat_path function Omair Javaid
2019-01-29  5:03 ` [RFC PATCH 1/6] Convert substitute_path_component to C++ Omair Javaid
2019-01-29  5:03 ` Omair Javaid [this message]
2019-01-29  5:04 ` [RFC PATCH 6/6] Linux kernel thread awareness AArch64 target support Omair Javaid
2019-01-29  5:04 ` [RFC PATCH 5/6] Linux kernel thread awareness Arm " Omair Javaid
2019-01-29  5:04 ` [RFC PATCH 4/6] Linux kernel debug infrastructure and target Linux kernel Omair Javaid
2019-01-29 17:50   ` John Baldwin
2019-01-31 11:43     ` Philipp Rudo
2019-01-31 16:14   ` Philipp Rudo
2019-02-04  9:35     ` Omair Javaid
2019-02-05 14:15       ` Philipp Rudo
2019-02-08  8:53         ` Omair Javaid
     [not found] ` <6c29e316-f1cb-ee65-bc0b-844cba5d74ad@FreeBSD.org>
2019-01-30 15:02   ` [RFC PATCH 0/6] Support for Linux kernel thread aware debug Andreas Arnez
2019-02-04  9:13   ` Omair Javaid
2019-02-04 17:52     ` John Baldwin
2019-02-08  8:54       ` Omair Javaid
2019-03-07 11:50         ` Omair Javaid

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=1548738199-9403-4-git-send-email-omair.javaid@linaro.org \
    --to=omair.javaid@linaro.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kieran@linuxembedded.co.uk \
    --cc=palves@redhat.com \
    --cc=peter.griffin@linaro.org \
    --cc=prudo@linux.ibm.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