Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/4] Tweak get_number related code
Date: Wed, 05 Mar 2014 12:49:00 -0000	[thread overview]
Message-ID: <1394023608-10761-1-git-send-email-yao@codesourcery.com> (raw)

Hi,
When I work on a patch using get_number in MI, I realize that code on
using get_number should be cleaned up first.  This patch series is
part of this cleanup, and I think they can be submitted first.  Each
patch in this series is quite independent.  Changes are obvious but
review is welcome too.

Regression tested on x86_64-linux.

*** BLURB HERE ***

Yao Qi (4):
  Add a newline in output messages
  Error on bad count number
  Handle parse number error in goto_bookmark_command
  Remove argument optional_p from get_tracepoint_by_number

 gdb/breakpoint.c                      |   26 ++++++++++++--------------
 gdb/breakpoint.h                      |    3 +--
 gdb/cli/cli-utils.c                   |    2 +-
 gdb/reverse.c                         |    7 ++++++-
 gdb/testsuite/gdb.base/ena-dis-br.exp |    5 +++++
 gdb/tracepoint.c                      |    2 +-
 6 files changed, 26 insertions(+), 19 deletions(-)

-- 
1.7.7.6


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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 12:49 Yao Qi [this message]
2014-03-05 12:49 ` [PATCH 4/4] Remove argument optional_p from get_tracepoint_by_number Yao Qi
2014-03-05 14:44   ` Joel Brobecker
2014-03-05 12:49 ` [PATCH 3/4] Handle parse number error in goto_bookmark_command Yao Qi
2014-03-05 14:38   ` Joel Brobecker
2014-03-06  7:10     ` Yao Qi
2014-03-05 12:49 ` [PATCH 2/4] Error on bad count number Yao Qi
2014-03-05 14:29   ` Joel Brobecker
2014-03-05 15:59     ` Pedro Alves
2014-03-06  9:56       ` Yao Qi
2014-03-06 12:21         ` Pedro Alves
2014-03-06 13:24           ` Joel Brobecker
2014-03-07  9:40           ` Yao Qi
2014-03-07 10:53             ` Eli Zaretskii
2014-03-07 11:09               ` Yao Qi
2014-03-07 13:27             ` Pedro Alves
2014-03-07 13:50               ` Joel Brobecker
2014-03-10  2:01               ` Yao Qi
2014-03-06 13:26       ` Joel Brobecker
2014-03-05 12:49 ` [OBV PATCH 1/4] Add a newline in output messages Yao Qi
2014-03-05 14:22   ` Joel Brobecker
2014-03-06  6:45     ` Yao Qi

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=1394023608-10761-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.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