From: Markus Metzger <markus.t.metzger@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com
Subject: [PATCH v3 0/5] thread, btrace: allow "record btrace" for running threads
Date: Mon, 30 Jan 2017 10:05:00 -0000 [thread overview]
Message-ID: <1485770743-6603-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.
Versions 2 and 3 check whether registers can be accessed before making the request
to gdbserver based on feedback from Pedro.
Version 3 addresses Pedro's feedback and adds more patches to address test suite
issues that were identified during reviews.
Markus Metzger (5):
thread: add can_access_registers_ptid
btrace: allow recording to be started (and stopped) for running
threads
btrace: add unsupported/untested messages when skipping tests
btrace, testsuite: fix extended-remote non-stop test
btrace, testsuite: fix extended-remote fail
gdb/btrace.c | 46 ++++++++++-
gdb/gdbthread.h | 4 +
gdb/testsuite/gdb.btrace/buffer-size.exp | 8 +-
gdb/testsuite/gdb.btrace/data.exp | 9 ++-
gdb/testsuite/gdb.btrace/delta.exp | 9 ++-
gdb/testsuite/gdb.btrace/dlopen.exp | 16 +++-
gdb/testsuite/gdb.btrace/enable-running.c | 47 +++++++++++
gdb/testsuite/gdb.btrace/enable-running.exp | 90 ++++++++++++++++++++++
gdb/testsuite/gdb.btrace/enable.exp | 17 +++-
gdb/testsuite/gdb.btrace/exception.exp | 9 ++-
gdb/testsuite/gdb.btrace/function_call_history.exp | 10 ++-
gdb/testsuite/gdb.btrace/gcore.exp | 8 +-
gdb/testsuite/gdb.btrace/instruction_history.exp | 9 ++-
gdb/testsuite/gdb.btrace/multi-thread-step.exp | 9 ++-
gdb/testsuite/gdb.btrace/nohist.exp | 8 +-
gdb/testsuite/gdb.btrace/non-stop.exp | 16 ++--
gdb/testsuite/gdb.btrace/reconnect.exp | 10 ++-
gdb/testsuite/gdb.btrace/record_goto-step.exp | 9 ++-
gdb/testsuite/gdb.btrace/record_goto.exp | 10 ++-
gdb/testsuite/gdb.btrace/rn-dl-bind.exp | 9 ++-
gdb/testsuite/gdb.btrace/segv.exp | 8 +-
gdb/testsuite/gdb.btrace/step.exp | 9 ++-
gdb/testsuite/gdb.btrace/stepi.exp | 14 ++--
gdb/testsuite/gdb.btrace/tailcall-only.exp | 10 ++-
gdb/testsuite/gdb.btrace/tailcall.exp | 9 ++-
gdb/testsuite/gdb.btrace/tsx.exp | 14 +++-
gdb/testsuite/gdb.btrace/unknown_functions.exp | 9 ++-
gdb/testsuite/gdb.btrace/vdso.exp | 9 ++-
gdb/thread.c | 20 +++++
29 files changed, 371 insertions(+), 84 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-30 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 10:05 Markus Metzger [this message]
2017-01-30 10:05 ` [PATCH v3 4/5] btrace, testsuite: fix extended-remote non-stop test Markus Metzger
2017-01-31 13:00 ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 3/5] btrace: add unsupported/untested messages when skipping tests Markus Metzger
2017-01-31 13:00 ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 2/5] btrace: allow recording to be started (and stopped) for running threads Markus Metzger
2017-01-31 12:59 ` Pedro Alves
2017-01-31 16:06 ` Metzger, Markus T
2017-01-31 16:36 ` Pedro Alves
2017-02-01 8:53 ` Metzger, Markus T
2017-02-01 9:08 ` Metzger, Markus T
2017-02-01 10:40 ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 5/5] btrace, testsuite: fix extended-remote fail Markus Metzger
2017-01-31 13:00 ` Pedro Alves
2017-01-31 16:06 ` Metzger, Markus T
2017-01-31 16:42 ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 1/5] thread: add can_access_registers_ptid Markus Metzger
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=1485770743-6603-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