import gdb-19990422 snapshot
[deliverable/binutils-gdb.git] / gdb / testsuite / gdb.hp / reg-test.exp
1 # Copyright (C) 1998 Free Software Foundation, Inc.
2
3 # This program is free software; you can redistribute it and/or modify
4 # it under the terms of the GNU General Public License as published by
5 # the Free Software Foundation; either version 2 of the License, or
6 # (at your option) any later version.
7 #
8 # This program is distributed in the hope that it will be useful,
9 # but WITHOUT ANY WARRANTY; without even the implied warranty of
10 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
11 # GNU General Public License for more details.
12 #
13 # You should have received a copy of the GNU General Public License
14 # along with this program; if not, write to the Free Software
15 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
16
17 # Please email any bugs, comments, and/or additions to this file to:
18 # bug-gdb@prep.ai.mit.edu
19
20 # Tests of wide register displays for GDB on HPPA 2.0 machines
21
22 # use this to debug:
23 #log_user 1
24
25 if $tracelevel then {
26 strace $tracelevel
27 }
28
29 if { [skip_hp_tests] } then { continue }
30
31 set testfile "reg-test"
32 set srcfile ${testfile}.s
33 set binfile ${objdir}/${subdir}/${testfile}
34
35 # To build a pa 2.0 executable
36 #
37 # as -o reg_test reg_test.s
38 # or
39 # cc -g -o reg_test reg_test.s
40 #
41 # The +DA2.0N flag doesn't seem to be needed.
42 #
43 # Don't reject if there are warnings, as we expect this warning:
44 #
45 # (Warning) At least one PA 2.0 object file (pa2.0_test2.o) was detected.
46 # The linked output may not run on a PA 1.x system.
47 #
48
49 if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
50 gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
51 }
52
53 gdb_exit
54 gdb_start
55 gdb_reinitialize_dir $srcdir/$subdir
56 gdb_load ${binfile}
57
58 # test machine--there's no 2.0n architecture, so we have
59 # to try to run the app.
60 #
61 send_gdb "break main\n"
62 gdb_expect {
63 -re "Breakpoint.*$gdb_prompt $" {
64 pass "initial set-up"
65 }
66 -re ".*$gdb_prompt $" {
67 fail "initial set-up"
68 }
69 timeout {
70 fail "initial set-up (timeout)"
71 }
72 }
73
74 send_gdb "run\n"
75 gdb_expect {
76 -re ".*Executable file incompatible with hardware.*$gdb_prompt $" {
77 # Not hppa2.0 machine
78 #
79 return 0
80 }
81 -re "Cannot exec.*$gdb_prompt $" {
82 # Not hppa2.0 machine
83 #
84 return 0
85 }
86 -re ".*Starting program:.*$gdb_prompt $" {
87 pass "Ready to start test"
88 }
89 timeout {
90 fail "initial set-up, part 2 (timeout)"
91 return 0
92 }
93 }
94
95 # Let the program set known values. This secretly deletes
96 # the breakpoint at main and re-runs to mainend.
97 #
98 runto mainend
99
100 # Look for known values
101 #
102 gdb_test "info reg r1" "r1 1"
103 gdb_test "info reg r4" "r4 2"
104 gdb_test "info reg r5" "r5 4"
105 gdb_test "info reg r6" "r6 8"
106 gdb_test "info reg r7" "r7 10"
107 gdb_test "info reg r8" "r8 20"
108 gdb_test "info reg r9" "r9 40"
109 gdb_test "info reg r10" "r10 80"
110 gdb_test "info reg r11" "r11 100"
111 gdb_test "info reg r12" "r12 200"
112 gdb_test "info reg r13" "r13 400"
113 gdb_test "info reg r14" "r14 800"
114 gdb_test "info reg r15" "r15 1000"
115 gdb_test "info reg r16" "r16 2000"
116
117 # Two odd variants that GDB supports are:
118 # "1" means "r1", and
119 # "$1" means "r1"
120 #
121 gdb_test "info reg 1 4" "r1 1.*r4 2"
122 gdb_test "info reg \$1" "r1 1"
123
124 # Verify that GDB responds gracefully to a register ID number that
125 # is out of range.
126 #
127 gdb_test "info reg 999" "999: invalid register"
128
129 # Make sure the floating point status and error registers
130 # don't show up as floating point numbers!
131 #
132 gdb_test "info reg fpsr" ".*fpsr 0.*" "fpsr"
133 gdb_test "info reg fpe1" ".*fpe1 0.*" "fpe1"
134 gdb_test "info reg fpe2" ".*fpe2 0.*" "fpe2"
135 gdb_test "info reg fpe3" ".*fpe3 0.*" "fpe3"
136 gdb_test "info reg fpe4" ".*fpe4 0.*" "fpe4"
137 gdb_test "info reg fpe5" ".*fpe5 0.*" "fpe5"
138 gdb_test "info reg fpe6" ".*fpe6 0.*" "fpe6"
139 gdb_test "info reg fpe7" ".*fpe7 0.*" "fpe7"
140
141 gdb_test "info reg fr4" ".*fr4.*(double precision).* 1"
142 gdb_test "info reg fr5" ".*fr5.*(double precision).* 2"
143 gdb_test "info reg fr6" ".*fr6.*(double precision).* 2"
144 gdb_test "info reg fr7" ".*fr7.*(double precision).* 4"
145 gdb_test "info reg fr8" ".*fr8.*(double precision).* 8"
146 gdb_test "info reg fr9" ".*fr9.*(double precision).* 32"
147 gdb_test "info reg fr10" ".*fr10.*(double precision).* 256"
148
149 gdb_test "info reg r19" "r19 deadbeefbadcadee"
150
151 # Need to add test of use of $<register-name>
152 #
153 # Q: How do you say a literal "$" in expect?
154 # A: You say "\$". A literal "\" is "\\".
155 #
156 # Please note that this test will fail as long as we are running
157 # in 32-bit mode: it will produce "$1 = 0xbadcadee". To fix it
158 # would require building a real 64-bit gdb (expression evaluation,
159 # in particular).
160 #
161 send_gdb "p/x \$r19\n"
162 gdb_expect {
163 -re ".*= 0xdeadbeefbadcadee.*$gdb_prompt $" {
164 pass "64-bit works"
165 }
166 -re ".*= 0xbadcadee.*$gdb_prompt $" {
167 pass "32-bit extract when using PRINT; expected but not good"
168 }
169 -re ".*$gdb_prompt $" {
170 fail "didn't print any part of right value"
171 }
172 timeout {
173 fail "timeout on print"
174 }
175 }
176
177 # Need to add tests of setting wide regs too. E.g.
178 #
179 # set $r4 = 0x1234567890123456
180 # p/x $r4
181 #
182
183 # done
184 #
185 gdb_exit
186 remote_exec build "rm -f ${binfile}"
187 return 0
This page took 0.043609 seconds and 4 git commands to generate.