[PATCH 0/5] Return error code in get_number

Yao Qi
2014-03-13T02:35:13Z

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