public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH] gdb/fortran/testsuite: print values and types of string variables
Date: Fri, 11 Nov 2022 16:51:22 +0000	[thread overview]
Message-ID: <df8d708ebf6b048f2c716ca444d9a0121220a2ab.1668185475.git.aburgess@redhat.com> (raw)

While looking through the Fortran tests, I couldn't find a test of GDB
printing the value and type of a Fortran string defined using the
'character*SIZE' notation.

This works fine in GDB right now, but I thought it wouldn't hurt to
have a test for this, so this commit adds such a test.
---
 gdb/testsuite/gdb.fortran/string-types.exp | 64 ++++++++++++++++++++++
 gdb/testsuite/gdb.fortran/string-types.f90 | 36 ++++++++++++
 2 files changed, 100 insertions(+)
 create mode 100644 gdb/testsuite/gdb.fortran/string-types.exp
 create mode 100644 gdb/testsuite/gdb.fortran/string-types.f90

diff --git a/gdb/testsuite/gdb.fortran/string-types.exp b/gdb/testsuite/gdb.fortran/string-types.exp
new file mode 100644
index 00000000000..73899e00605
--- /dev/null
+++ b/gdb/testsuite/gdb.fortran/string-types.exp
@@ -0,0 +1,64 @@
+# Copyright 2022 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/>.
+
+# Test print the value, and type, of Fortran string variables declared in
+# different ways in the test program.
+
+standard_testfile .f90
+load_lib fortran.exp
+
+if {[skip_fortran_tests]} { return -1 }
+
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile \
+	 {debug f90 quiet}]} {
+    return -1
+}
+
+if ![fortran_runto_main] then {
+    perror "Couldn't run to main"
+    return
+}
+
+gdb_breakpoint [gdb_get_line_number "First breakpoint"]
+gdb_breakpoint [gdb_get_line_number "Second breakpoint"]
+gdb_breakpoint [gdb_get_line_number "Third breakpoint"]
+
+with_test_prefix "first breakpoint" {
+    # Continue to the first breakpoint.
+    gdb_continue_to_breakpoint "continue"
+    gdb_test "print s" " = 'foo'"
+    gdb_test "ptype s" "type = character\\*3"
+}
+
+with_test_prefix "second breakpoint" {
+    # Continue to the second breakpoint.
+    gdb_continue_to_breakpoint "continue"
+    gdb_test "print s" " = 'foo'"
+    gdb_test "ptype s" "type = character\\*3"
+}
+
+with_test_prefix "third breakpoint, first time" {
+    # Continue to the third breakpoint.
+    gdb_continue_to_breakpoint "continue"
+    gdb_test "print s" " = 'foo'"
+    gdb_test "ptype s" "type = character \\(3\\)"
+}
+
+with_test_prefix "third breakpoint, second time" {
+    # Continue to the third breakpoint again.
+    gdb_continue_to_breakpoint "continue"
+    gdb_test "print s" " = 'foobar'"
+    gdb_test "ptype s" "type = character \\(6\\)"
+}
diff --git a/gdb/testsuite/gdb.fortran/string-types.f90 b/gdb/testsuite/gdb.fortran/string-types.f90
new file mode 100644
index 00000000000..c689c21e114
--- /dev/null
+++ b/gdb/testsuite/gdb.fortran/string-types.f90
@@ -0,0 +1,36 @@
+! Copyright 2022 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/>.
+
+subroutine fixed_size_string_v1(s)
+  character*3 s
+  print *, ""	! First breakpoint.
+end subroutine fixed_size_string_v1
+
+subroutine fixed_size_string_v2(s)
+  character(3) s
+  print *, ""	! Second breakpoint.
+end subroutine fixed_size_string_v2
+
+subroutine variable_size_string(s)
+  character*(*) s
+  print *, ""	! Third breakpoint.
+end subroutine variable_size_string
+
+program test
+  call fixed_size_string_v1('foo')
+  call fixed_size_string_v2('foo')
+  call variable_size_string('foo')
+  call variable_size_string('foobar')
+end program test

base-commit: db2e277d1a840091f56185d94f9d39c6736d2556
-- 
2.25.4


             reply	other threads:[~2022-11-11 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 16:51 Andrew Burgess [this message]
2022-11-16 16:34 ` Tom Tromey
2022-11-17 10:27   ` Andrew Burgess

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=df8d708ebf6b048f2c716ca444d9a0121220a2ab.1668185475.git.aburgess@redhat.com \
    --to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).