From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/4] gdbserver: Fix support for S390 TDB
Date: Fri, 12 Dec 2014 10:17:00 -0000 [thread overview]
Message-ID: <1418379431-14407-1-git-send-email-arnez@linux.vnet.ibm.com> (raw)
Last version here:
https://sourceware.org/ml/gdb-patches/2014-12/msg00193.html
New in v4:
* Removed the #ifndef IN_PROCESS_AGENT in get_thread_regcache, since
the whole routine is already under the same #ifndef.
* Added a comment to the handling of ENODATA from ptrace.
* Split out support for read-only regsets into a separate patch (now
patch #3).
Andreas Arnez (4):
gdbserver: Rephrase loops in regsets_fetch/store_inferior_registers
gdbserver: Prevent stale/random values in register cache
gdbserver: Support read-only regsets in linux-low.c
S390: Fix gdbserver support for TDB
gdb/gdbserver/linux-low.c | 42 ++++++++++++++++++------------------------
gdb/gdbserver/linux-s390-low.c | 31 +++++++++++++++++++++----------
gdb/gdbserver/regcache.c | 3 +++
3 files changed, 42 insertions(+), 34 deletions(-)
--
1.8.4.2
next reply other threads:[~2014-12-12 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:17 Andreas Arnez [this message]
2014-12-12 10:17 ` [PATCH v4 1/4] gdbserver: Rephrase loops in regsets_fetch/store_inferior_registers Andreas Arnez
2014-12-12 12:04 ` Pedro Alves
2014-12-12 10:18 ` [PATCH v4 3/4] gdbserver: Support read-only regsets in linux-low.c Andreas Arnez
2014-12-12 12:21 ` Pedro Alves
2014-12-12 10:18 ` [PATCH v4 2/4] gdbserver: Prevent stale/random values in register cache Andreas Arnez
2014-12-12 12:14 ` Pedro Alves
2014-12-12 10:19 ` [PATCH v4 4/4] S390: Fix gdbserver support for TDB Andreas Arnez
2014-12-12 12:23 ` 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=1418379431-14407-1-git-send-email-arnez@linux.vnet.ibm.com \
--to=arnez@linux.vnet.ibm.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