]> git.ipfire.org Git - thirdparty/binutils-gdb.git/blame - gdb/testsuite/gdb.hp/gdb.base-hp/reg.exp
import gdb-1999-08-16 snapshot
[thirdparty/binutils-gdb.git] / gdb / testsuite / gdb.hp / gdb.base-hp / reg.exp
CommitLineData
7be570e7
JM
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
25if $tracelevel then {
26 strace $tracelevel
27 }
28
29if { [skip_hp_tests] } then { continue }
30
31set testfile "reg"
32
33if [istarget "hppa2.0w-hp-hpux*"] {
34 verbose "reg.exp is not for PA2.0W."
35 return 0
36}
37set srcfile ${testfile}.s
38set binfile ${objdir}/${subdir}/${testfile}
39
40# To build a pa 2.0 executable
41#
42# as -o reg reg.s
43# or
44# cc -g -o reg reg.s
45#
46# The +DA2.0N flag doesn't seem to be needed.
47#
48# Don't reject if there are warnings, as we expect this warning:
49#
50# (Warning) At least one PA 2.0 object file (pa2.0_test2.o) was detected.
51# The linked output may not run on a PA 1.x system.
52#
53
54if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
55 gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
56}
57
58gdb_exit
59gdb_start
60gdb_reinitialize_dir $srcdir/$subdir
61gdb_load ${binfile}
62
63# test machine--there's no 2.0n architecture, so we have
64# to try to run the app.
65#
66send_gdb "break main\n"
67 gdb_expect {
68 -re "Breakpoint.*$gdb_prompt $" {
69 pass "initial set-up"
70 }
71 -re ".*$gdb_prompt $" {
72 fail "initial set-up"
73 }
74 timeout {
75 fail "initial set-up (timeout)"
76 }
77 }
78
79send_gdb "run\n"
80 gdb_expect {
81 -re ".*Executable file incompatible with hardware.*$gdb_prompt $" {
82 # Not hppa2.0 machine
83 #
84 return 0
85 }
86 -re "Cannot exec.*$gdb_prompt $" {
87 # Not hppa2.0 machine
88 #
89 return 0
90 }
91 -re ".*Starting program:.*$gdb_prompt $" {
92 pass "Ready to start test"
93 }
94 timeout {
95 fail "initial set-up, part 2 (timeout)"
96 return 0
97 }
98 }
99
100# Let the program set known values. This secretly deletes
101# the breakpoint at main and re-runs to mainend.
102#
103runto mainend
104
105# Look for known values
106#
107gdb_test "info reg r1" "r1 1"
108gdb_test "info reg r4" "r4 2"
109gdb_test "info reg r5" "r5 4"
110gdb_test "info reg r6" "r6 8"
111gdb_test "info reg r7" "r7 10"
112gdb_test "info reg r8" "r8 20"
113gdb_test "info reg r9" "r9 40"
114gdb_test "info reg r10" "r10 80"
115gdb_test "info reg r11" "r11 100"
116gdb_test "info reg r12" "r12 200"
117gdb_test "info reg r13" "r13 400"
118gdb_test "info reg r14" "r14 800"
119gdb_test "info reg r15" "r15 1000"
120gdb_test "info reg r16" "r16 2000"
121
122# Two odd variants that GDB supports are:
123# "1" means "r1", and
124# "$1" means "r1"
125#
126gdb_test "info reg 1 4" "r1 1.*r4 2"
127gdb_test "info reg \$1" "r1 1"
128
129# Verify that GDB responds gracefully to a register ID number that
130# is out of range.
131#
132gdb_test "info reg 999" "999: invalid register"
133
134# Make sure the floating point status and error registers
135# don't show up as floating point numbers!
136#
137gdb_test "info reg fpsr" ".*fpsr 0.*" "fpsr"
138gdb_test "info reg fpe1" ".*fpe1 0.*" "fpe1"
139gdb_test "info reg fpe2" ".*fpe2 0.*" "fpe2"
140gdb_test "info reg fpe3" ".*fpe3 0.*" "fpe3"
141gdb_test "info reg fpe4" ".*fpe4 0.*" "fpe4"
142gdb_test "info reg fpe5" ".*fpe5 0.*" "fpe5"
143gdb_test "info reg fpe6" ".*fpe6 0.*" "fpe6"
144gdb_test "info reg fpe7" ".*fpe7 0.*" "fpe7"
145
146gdb_test "info reg fr4" ".*fr4.*(double precision).* 1"
147gdb_test "info reg fr5" ".*fr5.*(double precision).* 2"
148gdb_test "info reg fr6" ".*fr6.*(double precision).* 2"
149gdb_test "info reg fr7" ".*fr7.*(double precision).* 4"
150gdb_test "info reg fr8" ".*fr8.*(double precision).* 8"
151gdb_test "info reg fr9" ".*fr9.*(double precision).* 32"
152gdb_test "info reg fr10" ".*fr10.*(double precision).* 256"
153
154gdb_test "info reg r19" "r19 deadbeefbadcadee"
155
156# Need to add test of use of $<register-name>
157#
158# Q: How do you say a literal "$" in expect?
159# A: You say "\$". A literal "\" is "\\".
160#
161# Please note that this test will fail as long as we are running
162# in 32-bit mode: it will produce "$1 = 0xbadcadee". To fix it
163# would require building a real 64-bit gdb (expression evaluation,
164# in particular).
165#
166send_gdb "p/x \$r19\n"
167 gdb_expect {
168 -re ".*= 0xdeadbeefbadcadee.*$gdb_prompt $" {
169 pass "64-bit works"
170 }
171 -re ".*= 0xbadcadee.*$gdb_prompt $" {
172 pass "32-bit extract when using PRINT; expected but not good"
173 }
174 -re ".*$gdb_prompt $" {
175 fail "didn't print any part of right value"
176 }
177 timeout {
178 fail "timeout on print"
179 }
180 }
181
182# Need to add tests of setting wide regs too. E.g.
183#
184# set $r4 = 0x1234567890123456
185# p/x $r4
186#
187
188# done
189#
190gdb_exit
191
192return 0