From: Markus Metzger <markus.t.metzger@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com
Subject: [PATCH v2 0/2] thread, btrace: allow "record btrace" for running threads
Date: Fri, 20 Jan 2017 14:39:00 -0000 [thread overview]
Message-ID: <1484923135-31270-1-git-send-email-markus.t.metzger@intel.com> (raw)
This refers to: https://sourceware.org/ml/gdb-patches/2016-11/msg00994.html.
The first version tried to detect the error in gdbserver, propagate it back, and
handle it in btrace.
This version checks whether registers can be accessed before making the request
to gdbserver based on feedback from Pedro.
Markus Metzger (2):
thread: add can_access_registers_ptid
btrace: allow recording to be started for running threads
gdb/btrace.c | 44 ++++++++++++++++--
gdb/gdbthread.h | 4 ++
gdb/testsuite/gdb.btrace/enable-running.c | 47 +++++++++++++++++++
gdb/testsuite/gdb.btrace/enable-running.exp | 72 +++++++++++++++++++++++++++++
gdb/thread.c | 20 ++++++++
5 files changed, 183 insertions(+), 4 deletions(-)
create mode 100644 gdb/testsuite/gdb.btrace/enable-running.c
create mode 100644 gdb/testsuite/gdb.btrace/enable-running.exp
--
1.8.3.1
next reply other threads:[~2017-01-20 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 14:39 Markus Metzger [this message]
2017-01-20 14:39 ` [PATCH v2 2/2] btrace: allow recording to be started " Markus Metzger
2017-01-25 14:32 ` Pedro Alves
2017-01-25 14:36 ` Pedro Alves
2017-01-25 15:53 ` Metzger, Markus T
2017-01-25 16:13 ` Pedro Alves
2017-01-26 14:54 ` Metzger, Markus T
2017-01-20 14:39 ` [PATCH v2 1/2] thread: add can_access_registers_ptid Markus Metzger
2017-01-25 14:33 ` Pedro Alves
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=1484923135-31270-1-git-send-email-markus.t.metzger@intel.com \
--to=markus.t.metzger@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