public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 1/4] [gdb/testsuite] Add gdb.testsuite/gdb-caching-proc.exp
Date: Sat,  4 Mar 2023 10:35:46 +0100	[thread overview]
Message-ID: <20230304093549.8689-1-tdevries@suse.de> (raw)

Add test-case gdb.testsuite/gdb-caching-proc.exp that excercises
gdb_caching_proc.

Tested on x86_64-linux.
---
 .../gdb.testsuite/gdb-caching-proc.exp        | 38 +++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 gdb/testsuite/gdb.testsuite/gdb-caching-proc.exp

diff --git a/gdb/testsuite/gdb.testsuite/gdb-caching-proc.exp b/gdb/testsuite/gdb.testsuite/gdb-caching-proc.exp
new file mode 100644
index 00000000000..de35c046185
--- /dev/null
+++ b/gdb/testsuite/gdb.testsuite/gdb-caching-proc.exp
@@ -0,0 +1,38 @@
+# Copyright 2023 Free Software Foundation, Inc.
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+gdb_caching_proc gdb_testsuite_gdb_caching_proc_exp_noarg {
+    incr ::count
+    return 1
+}
+
+set assertions {
+    { [gdb_testsuite_gdb_caching_proc_exp_noarg] == 1 }
+}
+
+set assertion_nr 0
+foreach assertion $assertions {
+    with_test_prefix $assertion_nr {
+	set ::count 0
+
+	gdb_assert $assertion
+	gdb_assert { $::count == 1 }
+
+	with_test_prefix cached {
+	    gdb_assert $assertion
+	    gdb_assert { $::count == 1 }
+	}
+    }
+    incr assertion_nr
+}

base-commit: 9c2c346137eeca000840023b6d9340274da7a905
-- 
2.35.3


             reply	other threads:[~2023-03-04  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04  9:35 Tom de Vries [this message]
2023-03-04  9:35 ` [PATCH v2 2/4] [gdb/testsuite] Use regular proc syntax for gdb_caching_proc Tom de Vries
2023-03-06 14:20   ` Tom Tromey
2023-03-04  9:35 ` [PATCH v2 3/4] [gdb/testsuite] Allow args in gdb_caching_proc Tom de Vries
2023-03-06 14:23   ` Tom Tromey
2023-03-04  9:35 ` [PATCH v2 4/4] [gdb/testsuite] Move gdb.base/gdb-caching-proc.exp to gdb.testsuite Tom de Vries
2023-03-06 14:48   ` Tom Tromey
2023-03-06 15:45     ` Tom de Vries
2023-03-06 14:47 ` [PATCH v2 1/4] [gdb/testsuite] Add gdb.testsuite/gdb-caching-proc.exp 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=20230304093549.8689-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).