Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer
Date: Thu, 03 Nov 2016 14:33:00 -0000	[thread overview]
Message-ID: <20161103143300.24934-1-antoine.tremblay@ericsson.com> (raw)

Hi,

Since all the prerequisites for this series have been addressed,  
this is a V2 of https://sourceware.org/ml/gdb-patches/2016-01/msg00111.html

In this V2:
 - Re-based on a recent master
 - New patch 3 improves segmentation of trace and ftrace tests 
 - New patch 4 makes range-stepping.exp use FAST_TRACEPOINT_LABEL

Patch 2 is already OK see:
https://sourceware.org/ml/gdb-patches/2016-02/msg00867.html

Antoine Tremblay (5):
  Teach arm unwinders to terminate gracefully
  Enable tracing of pseudo-registers on ARM
  Improve tests to allow for targets that support trace but not ftrace
  Use FAST_TRACEPOINT_LABEL in range-stepping.exp
  Support tracepoints for ARM linux in GDBServer

 gdb/NEWS                                         |   2 +
 gdb/arm-tdep.c                                   | 210 ++++++++++++++++++-----
 gdb/doc/gdb.texinfo                              |  23 ++-
 gdb/gdbserver/linux-arm-low.c                    |  10 +-
 gdb/gdbserver/mem-break.c                        |  13 ++
 gdb/gdbserver/mem-break.h                        |   7 +
 gdb/gdbserver/server.c                           |   1 +
 gdb/gdbserver/tracepoint.c                       |  43 ++++-
 gdb/remote.c                                     |  27 +++
 gdb/testsuite/gdb.trace/change-loc.exp           |   5 +-
 gdb/testsuite/gdb.trace/collection.exp           |   7 +-
 gdb/testsuite/gdb.trace/ftrace-lock.exp          |   6 +-
 gdb/testsuite/gdb.trace/ftrace.exp               |   6 +-
 gdb/testsuite/gdb.trace/pending.exp              |   5 +-
 gdb/testsuite/gdb.trace/range-stepping.c         |  22 +--
 gdb/testsuite/gdb.trace/range-stepping.exp       |   6 +-
 gdb/testsuite/gdb.trace/trace-break.exp          |   6 +-
 gdb/testsuite/gdb.trace/trace-common.h           |  12 +-
 gdb/testsuite/gdb.trace/trace-condition.exp      |  64 ++++---
 gdb/testsuite/gdb.trace/trace-enable-disable.exp |  27 +--
 gdb/testsuite/gdb.trace/trace-mt.exp             |   5 +-
 gdb/testsuite/gdb.trace/tracefile-pseudo-reg.c   |  16 +-
 gdb/testsuite/gdb.trace/tracefile-pseudo-reg.exp |  35 +++-
 gdb/testsuite/lib/trace-support.exp              |   3 +
 24 files changed, 423 insertions(+), 138 deletions(-)

-- 
2.9.2


             reply	other threads:[~2016-11-03 14:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 14:33 Antoine Tremblay [this message]
2016-11-03 14:33 ` [PATCH V2 1/5] Teach arm unwinders to terminate gracefully Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 5/5] Support tracepoints for ARM linux in GDBServer Antoine Tremblay
2016-11-03 17:51   ` Eli Zaretskii
2016-11-03 18:12     ` Antoine Tremblay
2016-11-10 14:01   ` Yao Qi
2016-11-15 14:42     ` Antoine Tremblay
2016-11-16 20:49       ` Yao Qi
2016-11-03 14:33 ` [PATCH V2 3/5] Improve tests to allow for targets that support trace but not ftrace Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 4/5] Use FAST_TRACEPOINT_LABEL in range-stepping.exp Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 2/5] Enable tracing of pseudo-registers on ARM Antoine Tremblay
2016-11-07  9:25 ` [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer Yao Qi
     [not found]   ` <wwoka8dasqta.fsf@ericsson.com>
2016-11-08 15:34     ` Antoine Tremblay
2016-11-09 16:39     ` Yao Qi
2016-11-09 17:58       ` Antoine Tremblay

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=20161103143300.24934-1-antoine.tremblay@ericsson.com \
    --to=antoine.tremblay@ericsson.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