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 2/4] Error on bad count number
Date: Wed, 05 Mar 2014 12:49:00 -0000	[thread overview]
Message-ID: <1394023608-10761-3-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1394023608-10761-1-git-send-email-yao@codesourcery.com>

GDB is quiet for these invalid input like this

  (gdb) enable count 1.1 1
  (gdb)

This patch is to check the input number is valid, and emit error if
input number isn't valid.  With this patch, it becomes:

  (gdb) enable count 1.1 1
  Bad count number '1.1 1'

gdb:

2014-03-05  Yao Qi  <yao@codesourcery.com>

	* breakpoint.c (enable_count_command): Emit error if 'count'
	is zero.

gdb/testsuite:

2014-03-05  Yao Qi  <yao@codesourcery.com>

	* gdb.base/ena-dis-br.exp: Test bad count number.
---
 gdb/breakpoint.c                      |    4 ++++
 gdb/testsuite/gdb.base/ena-dis-br.exp |    5 +++++
 2 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 2f2c625..5dcaa0e 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -14934,8 +14934,12 @@ do_map_enable_count_breakpoint (struct breakpoint *bpt, void *countptr)
 static void
 enable_count_command (char *args, int from_tty)
 {
+  char *p = args;
   int count = get_number (&args);
 
+  if (count == 0)
+    error (_("Bad count number '%s'"), p);
+
   map_breakpoint_numbers (args, do_map_enable_count_breakpoint, &count);
 }
 
diff --git a/gdb/testsuite/gdb.base/ena-dis-br.exp b/gdb/testsuite/gdb.base/ena-dis-br.exp
index 6f2c469..4b83e56 100644
--- a/gdb/testsuite/gdb.base/ena-dis-br.exp
+++ b/gdb/testsuite/gdb.base/ena-dis-br.exp
@@ -169,6 +169,11 @@ gdb_test "continue" \
     ".*marker1 .*:($bp_location15|$bp_location16).*" \
     "continue through enable count, now disabled"
 
+# Test enable count with bad count number.
+
+gdb_test "enable count 1.1 $bp" "Bad count number '1.1 $bp'.*" \
+    "enable count with bad number"
+
 # Verify that we can set a breakpoint with an ignore count N, which
 # should cause the next N triggers of the bp to be ignored.  (This is
 # a flavor of enablement/disablement, after all.)
-- 
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 [PATCH 0/4] Tweak get_number related code Yao Qi
2014-03-05 12:49 ` Yao Qi [this message]
2014-03-05 14:29   ` [PATCH 2/4] Error on bad count number 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
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 4/4] Remove argument optional_p from get_tracepoint_by_number Yao Qi
2014-03-05 14:44   ` Joel Brobecker

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-3-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