public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: remove DOS line endings from a test script
Date: Mon, 28 Nov 2022 21:04:34 +0000 (GMT)	[thread overview]
Message-ID: <20221128210434.D48C53858C52@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e2afece894f0de7990997792e3781cf925a011a0

commit e2afece894f0de7990997792e3781cf925a011a0
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Mon Nov 14 14:25:47 2022 +0000

    gdb/testsuite: remove DOS line endings from a test script
    
    The gdb.fortran/nested-funcs.exp test script has DOS line endings.  I
    can see no reason why this script needs DOS line endings.
    
    Convert to UNIX line endings.
    
    There should be no change in what is tested after this commit.

Diff:
---
 gdb/testsuite/gdb.fortran/nested-funcs.exp | 184 ++++++++++++++---------------
 1 file changed, 92 insertions(+), 92 deletions(-)

diff --git a/gdb/testsuite/gdb.fortran/nested-funcs.exp b/gdb/testsuite/gdb.fortran/nested-funcs.exp
index d5ba7ce3c5e..ea3d66685be 100755
--- a/gdb/testsuite/gdb.fortran/nested-funcs.exp
+++ b/gdb/testsuite/gdb.fortran/nested-funcs.exp
@@ -1,92 +1,92 @@
-# Copyright 2016-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/>.
-
-# This testcase is supposed to test DWARF static link which is usually
-# used together with nested functions.  
-
-if { [skip_fortran_tests] } { return -1 }
-
-standard_testfile .f90
-load_lib "fortran.exp"
-
-if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug f90}]} {
-    return -1
-}
-
-if ![fortran_runto_main] then {
-    perror "couldn't run to main"
-    continue
-}
-
-# Test if we can set a breakpoint in a nested function
-gdb_breakpoint "testnestedfuncs::sub_nested_outer"
-gdb_continue_to_breakpoint "testnestedfuncs::sub_nested_outer" \
-    ".*local_int = 19"
-
-# Test if we can access local and
-# non-local variables defined one level up.
-gdb_breakpoint [gdb_get_line_number "! BP_outer"]
-gdb_continue_to_breakpoint "! BP_outer" ".*! BP_outer"
-gdb_test "print index" "= 13" "print index at BP_outer"
-gdb_test_no_output "set variable index = 42"
-gdb_test "print index" "= 42" "print index at BP_outer, manipulated"
-gdb_test "print local_int" "= 19" "print local_int in outer function"
-
-# Non-local variable should be affected in one frame up as well.
-gdb_test "up"
-gdb_test "print index" "= 42" "print index at BP1, one frame up"
-
-# Test if we can set a breakpoint in a nested function
-gdb_breakpoint "testnestedfuncs::sub_nested_inner"
-gdb_continue_to_breakpoint "testnestedfuncs::sub_nested_inner" \
-    ".*local_int = 17"
-
-# Test if we can access local and
-# non-local variables defined two level up.
-gdb_breakpoint [gdb_get_line_number "! BP_inner"]
-gdb_continue_to_breakpoint "! BP_inner" ".*! BP_inner"
-gdb_test "print index" "= 42" "print index at BP_inner"
-gdb_test "print v_state%code" "= 61" "print v_state%code at BP_inner"
-gdb_test "print local_int" "= 17" "print local_int in inner function"
-
-# Test if local variable is still correct.
-gdb_breakpoint [gdb_get_line_number "! BP_outer_2"]
-gdb_continue_to_breakpoint "! BP_outer_2" ".*! BP_outer_2"
-gdb_test "print local_int" "= 19" \
-  "print local_int in outer function, after sub_nested_inner"
-
-# Test if we can set a breakpoint in public routine with the same name
-# as the internal
-gdb_breakpoint "sub_nested_outer"
-gdb_continue_to_breakpoint "sub_nested_outer" \
-    ".*name = 'sub_nested_outer external'"
-
-# Test if we can set a breakpoint in public routine with the same name
-# as the internal
-gdb_breakpoint "sub_with_sub_nested_outer::sub_nested_outer"
-gdb_continue_to_breakpoint \
-    "sub_with_sub_nested_outer::sub_nested_outer" ".*local_int = 11"
-
-# Test if we can set a breakpoint in public routine with the same name
-# as the internal
-gdb_breakpoint "mod1::sub_nested_outer"
-gdb_continue_to_breakpoint "mod1::sub_nested_outer" \
-    ".*name = 'sub_nested_outer_mod1'"
-
-# Sanity check in main.
-gdb_breakpoint [gdb_get_line_number "! BP_main"]
-gdb_continue_to_breakpoint "! BP_main" ".*! BP_main"
-gdb_test "print index" "= 42" "print index at BP_main"
-gdb_test "print v_state%code" "= 59" "print v_state%code at BP_main"
+# Copyright 2016-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/>.
+
+# This testcase is supposed to test DWARF static link which is usually
+# used together with nested functions.  
+
+if { [skip_fortran_tests] } { return -1 }
+
+standard_testfile .f90
+load_lib "fortran.exp"
+
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug f90}]} {
+    return -1
+}
+
+if ![fortran_runto_main] then {
+    perror "couldn't run to main"
+    continue
+}
+
+# Test if we can set a breakpoint in a nested function
+gdb_breakpoint "testnestedfuncs::sub_nested_outer"
+gdb_continue_to_breakpoint "testnestedfuncs::sub_nested_outer" \
+    ".*local_int = 19"
+
+# Test if we can access local and
+# non-local variables defined one level up.
+gdb_breakpoint [gdb_get_line_number "! BP_outer"]
+gdb_continue_to_breakpoint "! BP_outer" ".*! BP_outer"
+gdb_test "print index" "= 13" "print index at BP_outer"
+gdb_test_no_output "set variable index = 42"
+gdb_test "print index" "= 42" "print index at BP_outer, manipulated"
+gdb_test "print local_int" "= 19" "print local_int in outer function"
+
+# Non-local variable should be affected in one frame up as well.
+gdb_test "up"
+gdb_test "print index" "= 42" "print index at BP1, one frame up"
+
+# Test if we can set a breakpoint in a nested function
+gdb_breakpoint "testnestedfuncs::sub_nested_inner"
+gdb_continue_to_breakpoint "testnestedfuncs::sub_nested_inner" \
+    ".*local_int = 17"
+
+# Test if we can access local and
+# non-local variables defined two level up.
+gdb_breakpoint [gdb_get_line_number "! BP_inner"]
+gdb_continue_to_breakpoint "! BP_inner" ".*! BP_inner"
+gdb_test "print index" "= 42" "print index at BP_inner"
+gdb_test "print v_state%code" "= 61" "print v_state%code at BP_inner"
+gdb_test "print local_int" "= 17" "print local_int in inner function"
+
+# Test if local variable is still correct.
+gdb_breakpoint [gdb_get_line_number "! BP_outer_2"]
+gdb_continue_to_breakpoint "! BP_outer_2" ".*! BP_outer_2"
+gdb_test "print local_int" "= 19" \
+  "print local_int in outer function, after sub_nested_inner"
+
+# Test if we can set a breakpoint in public routine with the same name
+# as the internal
+gdb_breakpoint "sub_nested_outer"
+gdb_continue_to_breakpoint "sub_nested_outer" \
+    ".*name = 'sub_nested_outer external'"
+
+# Test if we can set a breakpoint in public routine with the same name
+# as the internal
+gdb_breakpoint "sub_with_sub_nested_outer::sub_nested_outer"
+gdb_continue_to_breakpoint \
+    "sub_with_sub_nested_outer::sub_nested_outer" ".*local_int = 11"
+
+# Test if we can set a breakpoint in public routine with the same name
+# as the internal
+gdb_breakpoint "mod1::sub_nested_outer"
+gdb_continue_to_breakpoint "mod1::sub_nested_outer" \
+    ".*name = 'sub_nested_outer_mod1'"
+
+# Sanity check in main.
+gdb_breakpoint [gdb_get_line_number "! BP_main"]
+gdb_continue_to_breakpoint "! BP_main" ".*! BP_main"
+gdb_test "print index" "= 42" "print index at BP_main"
+gdb_test "print v_state%code" "= 59" "print v_state%code at BP_main"

                 reply	other threads:[~2022-11-28 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221128210434.D48C53858C52@sourceware.org \
    --to=aburgess@sourceware.org \
    --cc=gdb-cvs@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).