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/5] Return error code in get_number
Date: Thu, 13 Mar 2014 02:35:00 -0000	[thread overview]
Message-ID: <1394677950-4054-1-git-send-email-yao@codesourcery.com> (raw)

Patch #5 tries to teach GDB to accept convenience variable in MI
commands, in which we use get_number to parse string and get number.
However, get_number returns zero for any kinds of error, and callers
can't tell from it.  Patch #4 changes get_number's interface to
return parsing status and parsed number.  This patch also moves
some printing messages out of get_number, and let the callers to
print messages according to returned status.

Patch #1 - #3 are cleanups and each of them are independent.  This
series is tested on x86_64-linux.

*** BLURB HERE ***

Yao Qi (5):
  Remove argument 'state' from get_tracepoint_by_number
  Change argument 'args' of get_tracepoint_by_number to char *
  Emit wrong value error when parsing range
  get_number returns status in details
  Accept convenience variable in commands -break-passcount and
    -break-commands

 gdb/NEWS                                           |    5 +
 gdb/breakpoint.c                                   |   62 +++++++------
 gdb/breakpoint.h                                   |    3 +-
 gdb/cli/cli-utils.c                                |   94 ++++++++++++++------
 gdb/cli/cli-utils.h                                |   20 ++++-
 gdb/mi/mi-cmd-break.c                              |   26 ++++--
 gdb/reverse.c                                      |    6 +-
 gdb/testsuite/gdb.base/ena-dis-br.exp              |    9 ++
 gdb/testsuite/gdb.mi/mi-break.exp                  |    8 ++
 gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp     |    2 +
 .../gdb.trace/mi-trace-frame-collected.exp         |    4 +-
 gdb/testsuite/gdb.trace/mi-trace-unavailable.exp   |    4 +-
 gdb/tracepoint.c                                   |    2 +-
 13 files changed, 167 insertions(+), 78 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2014-03-13  2:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  2:35 Yao Qi [this message]
2014-03-13  2:35 ` [PATCH 3/5] Emit wrong value error when parsing range Yao Qi
2014-03-13  2:35 ` [PATCH 1/5] Remove argument 'state' from get_tracepoint_by_number Yao Qi
2014-03-13  2:35 ` [PATCH 4/5] get_number returns status in details Yao Qi
2014-03-13  2:35 ` [PATCH 5/5] Accept convenience variable in commands -break-passcount and -break-commands Yao Qi
2014-03-14  8:22   ` Eli Zaretskii
2014-03-13  2:35 ` [PATCH 2/5] Change argument 'args' of get_tracepoint_by_number to char * Yao Qi
2014-03-13 15:14 ` [PATCH 0/5] Return error code in get_number Tom Tromey
2014-03-14  0:59   ` Yao Qi
2014-03-14 14:38     ` Tom Tromey
2014-03-17  0:51       ` Yao Qi
2014-05-15 17:58         ` Tom Tromey

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=1394677950-4054-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