Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/2] Provide useful completer for "info registers"
Date: Thu, 11 Dec 2014 11:49:00 -0000	[thread overview]
Message-ID: <1418298589-23120-1-git-send-email-arnez@linux.vnet.ibm.com> (raw)

Last version here:

  https://sourceware.org/ml/gdb-patches/2014-12/msg00212.html

New in v4:

* In maintenance_print_user_registers, no longer require
  target_has_registers, but get the gdbarch with get_current_arch().

* Cosmetic changes in maintenance_print_user_registers: Rename the
  variable "nr" to "regnum"; increment regnum in the for-loop
  iterator instead of the loop body.

* In the documentation for the new command, enclose the first
  occurrence of "user registers" in @dfn{}.


Andreas Arnez (2):
  Add new GDB command "maint print user-registers"
  Provide completer for "info registers"

 gdb/NEWS                              |  3 +++
 gdb/completer.c                       | 42 +++++++++++++++++++++++++++++++++++
 gdb/completer.h                       |  3 +++
 gdb/doc/gdb.texinfo                   | 12 ++++++++++
 gdb/infcmd.c                          | 12 +++++++---
 gdb/testsuite/gdb.base/completion.exp | 31 ++++++++++++++++++++++++++
 gdb/user-regs.c                       | 24 ++++++++++++++++++++
 7 files changed, 124 insertions(+), 3 deletions(-)

-- 
1.8.4.2


             reply	other threads:[~2014-12-11 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:49 Andreas Arnez [this message]
2014-12-11 11:49 ` [PATCH v4 2/2] Provide " Andreas Arnez
2014-12-12 13:20   ` Pedro Alves
2014-12-12 15:20     ` Andreas Arnez
2014-12-12 15:30       ` Pedro Alves
2014-12-12 17:45       ` Doug Evans
2014-12-12 19:04         ` Andreas Arnez
2014-12-15 12:41           ` Pedro Alves
2014-12-11 11:49 ` [PATCH v4 1/2] Add new GDB command "maint print user-registers" Andreas Arnez
2014-12-12 13:19   ` 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=1418298589-23120-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