Commit | Line | Data |
---|---|---|
9b254dd1 | 1 | # Copyright 1997, 1998, 1999, 2007, 2008 Free Software Foundation, Inc. |
daf3f280 JM |
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 | |
e22f8b7c | 5 | # the Free Software Foundation; either version 3 of the License, or |
daf3f280 | 6 | # (at your option) any later version. |
e22f8b7c | 7 | # |
daf3f280 JM |
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. | |
e22f8b7c | 12 | # |
daf3f280 | 13 | # You should have received a copy of the GNU General Public License |
e22f8b7c | 14 | # along with this program. If not, see <http://www.gnu.org/licenses/>. */ |
daf3f280 JM |
15 | |
16 | # Please email any bugs, comments, and/or additions to this file to: | |
17 | # bug-gdb@prep.ai.mit.edu | |
18 | ||
19 | # This file was written by Fred Fish. (fnf@cygnus.com) | |
20 | ||
37225f62 JB |
21 | # These tests are the same as those in callfuncs.exp, except that the |
22 | # test program here does not call malloc. | |
23 | # | |
24 | # "What in the world does malloc have to do with calling functions in | |
25 | # the inferior?" Well, nothing. GDB's ability to invoke a function | |
26 | # in the inferior program works just fine in programs that have no | |
27 | # malloc function available. It doesn't rely on the inferior's | |
28 | # malloc, directly or indirectly. It just uses the inferior's stack | |
29 | # space. | |
30 | # | |
31 | # "Then what's the point of this test file?" Well, it just so happens | |
32 | # that this file, in addition to testing inferior function calls, also | |
33 | # tests GDB's ability to evaluate string literals (like "string 1" and | |
34 | # "string 2" in the tests below). Evaluating *those* sorts of | |
35 | # expressions does require malloc. | |
36 | # | |
37 | # (As an extension to C, GDB also has a syntax for literal arrays of | |
38 | # anything, not just characters. For example, the expression | |
39 | # {2,3,4,5} (which appears in the tests below) evaluates to an array | |
40 | # of four ints. So rather than talking just about string literals, | |
41 | # we'll use the broader term "array literals".) | |
42 | # | |
43 | # Now, in this file, we only evaluate array literals when we're about | |
44 | # to pass them to a function, but don't be confused --- this is a red | |
45 | # herring. You can evaluate "abcdef" even if you're not about to pass | |
46 | # that to a function, and doing so requires malloc even if you're just | |
47 | # going to store a pointer to it in a variable, like this: | |
48 | # | |
49 | # (gdb) ptype s | |
50 | # type = char * | |
51 | # (gdb) set variable s = "abcdef" | |
52 | # | |
53 | # According to C's rules for evaluating expressions, arrays are | |
54 | # converted into pointers to their first element. This means that, in | |
55 | # order to evaluate an expression like "abcdef", GDB needs to actually | |
56 | # find some memory in the inferior we can plop the characters into; | |
57 | # then we use that memory's address as the address of our array | |
58 | # literal. GDB finds this memory by calling the inferior's malloc | |
59 | # function, if it has one. So, evaluating an array literal depends on | |
60 | # performing an inferior function call, but not vice versa. (GDB | |
61 | # can't just allocate the space on the stack; the pointer may remain | |
62 | # live long after the current frame has been popped.) | |
63 | # | |
64 | # "But, if evaluating array literals requires malloc, what's the point | |
65 | # of testing that GDB can do so in a program that doesn't have malloc? | |
66 | # It can't work!" On most systems, that's right, but HP-UX has some | |
67 | # sort of dynamic linking magic that ensures that *every* program has | |
68 | # malloc. So on HP-UX, GDB can evaluate array literals even in | |
69 | # inferior programs that don't use malloc. That's why this test is in | |
70 | # gdb.hp. | |
71 | # | |
72 | # This file has, for some reason, led to well more than its fair share | |
73 | # of misunderstandings about the relationship between array literal | |
74 | # expressions and inferior function calls. Folks talk as if you can | |
75 | # only evaluate array literals when you're about to pass them to a | |
76 | # function. I think they're assuming that, since GDB is constructing | |
77 | # a new frame on the inferior's stack (correct), it's going to use | |
78 | # that space for the array literals (incorrect). Remember that those | |
79 | # array literals may need to be live long after the inferior function | |
80 | # call returns; GDB can't tell. | |
81 | # | |
82 | # What makes the confusion worse is that there *is* a relationship | |
83 | # between array literals and inferior function calls --- GDB uses | |
84 | # inferior function calls to evaluate array literals. But many people | |
85 | # jump to other, incorrect conclusions about this. | |
daf3f280 JM |
86 | |
87 | if $tracelevel then { | |
88 | strace $tracelevel | |
89 | } | |
90 | ||
91 | set prms_id 0 | |
92 | set bug_id 0 | |
93 | ||
37225f62 JB |
94 | if { [skip_hp_tests] } then { continue } |
95 | ||
daf3f280 JM |
96 | set testfile "callfwmall" |
97 | set srcfile ${testfile}.c | |
98 | set binfile ${objdir}/${subdir}/${testfile} | |
99 | ||
100 | if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } { | |
b60f0898 JB |
101 | untested callfwmall.exp |
102 | return -1 | |
daf3f280 JM |
103 | } |
104 | ||
105 | # Create and source the file that provides information about the compiler | |
106 | # used to compile the test case. | |
107 | ||
108 | if [get_compiler_info ${binfile}] { | |
109 | return -1; | |
110 | } | |
111 | ||
112 | if {$hp_aCC_compiler} { | |
113 | set prototypes 1 | |
114 | } else { | |
115 | set prototypes 0 | |
116 | } | |
117 | ||
118 | ||
9fbfe2dc AC |
119 | # Some targets can't call functions, so don't even bother with this |
120 | # test. | |
daf3f280 JM |
121 | if [target_info exists gdb,cannot_call_functions] { |
122 | setup_xfail "*-*-*" 2416 | |
123 | fail "This target can not call functions" | |
124 | continue | |
125 | } | |
126 | ||
127 | # Set the current language to C. This counts as a test. If it | |
128 | # fails, then we skip the other tests. | |
129 | ||
130 | proc set_lang_c {} { | |
131 | global gdb_prompt | |
132 | ||
133 | send_gdb "set language c\n" | |
134 | gdb_expect { | |
135 | -re ".*$gdb_prompt $" {} | |
136 | timeout { fail "set language c (timeout)" ; return 0 } | |
137 | } | |
138 | ||
139 | send_gdb "show language\n" | |
140 | gdb_expect { | |
141 | -re ".* source language is \"c\".*$gdb_prompt $" { | |
142 | pass "set language to \"c\"" | |
143 | return 1 | |
144 | } | |
145 | -re ".*$gdb_prompt $" { | |
146 | fail "setting language to \"c\"" | |
147 | return 0 | |
148 | } | |
149 | timeout { | |
150 | fail "can't show language (timeout)" | |
151 | return 0 | |
152 | } | |
153 | } | |
154 | } | |
155 | ||
156 | # FIXME: Before calling this proc, we should probably verify that | |
157 | # we can call inferior functions and get a valid integral value | |
158 | # returned. | |
159 | # Note that it is OK to check for 0 or 1 as the returned values, because C | |
160 | # specifies that the numeric value of a relational or logical expression | |
161 | # (computed in the inferior) is 1 for true and 0 for false. | |
162 | ||
163 | proc do_function_calls {} { | |
164 | global prototypes | |
165 | global gcc_compiled | |
a0b3c4fd JM |
166 | global gdb_prompt |
167 | ||
daf3f280 JM |
168 | # We need to up this because this can be really slow on some boards. |
169 | set timeout 60; | |
170 | ||
171 | gdb_test "p t_char_values(0,0)" " = 0" | |
172 | gdb_test "p t_char_values('a','b')" " = 1" | |
173 | gdb_test "p t_char_values(char_val1,char_val2)" " = 1" | |
174 | gdb_test "p t_char_values('a',char_val2)" " = 1" | |
175 | gdb_test "p t_char_values(char_val1,'b')" " = 1" | |
176 | ||
177 | gdb_test "p t_short_values(0,0)" " = 0" | |
178 | gdb_test "p t_short_values(10,-23)" " = 1" | |
179 | gdb_test "p t_short_values(short_val1,short_val2)" " = 1" | |
180 | gdb_test "p t_short_values(10,short_val2)" " = 1" | |
181 | gdb_test "p t_short_values(short_val1,-23)" " = 1" | |
182 | ||
183 | gdb_test "p t_int_values(0,0)" " = 0" | |
184 | gdb_test "p t_int_values(87,-26)" " = 1" | |
185 | gdb_test "p t_int_values(int_val1,int_val2)" " = 1" | |
186 | gdb_test "p t_int_values(87,int_val2)" " = 1" | |
187 | gdb_test "p t_int_values(int_val1,-26)" " = 1" | |
188 | ||
189 | gdb_test "p t_long_values(0,0)" " = 0" | |
190 | gdb_test "p t_long_values(789,-321)" " = 1" | |
191 | gdb_test "p t_long_values(long_val1,long_val2)" " = 1" | |
192 | gdb_test "p t_long_values(789,long_val2)" " = 1" | |
193 | gdb_test "p t_long_values(long_val1,-321)" " = 1" | |
194 | ||
195 | if ![target_info exists gdb,skip_float_tests] { | |
196 | gdb_test "p t_float_values(0.0,0.0)" " = 0" | |
197 | ||
198 | # These next four tests fail on the mn10300. | |
199 | # The first value is passed in regs, the other in memory. | |
200 | # Gcc emits different stabs for the two parameters; the first is | |
201 | # claimed to be a float, the second a double. | |
202 | # dbxout.c in gcc claims this is the desired behavior. | |
a0b3c4fd | 203 | setup_xfail "mn10300-*-*" |
daf3f280 | 204 | gdb_test "p t_float_values(3.14159,-2.3765)" " = 1" |
a0b3c4fd | 205 | setup_xfail "mn10300-*-*" |
daf3f280 | 206 | gdb_test "p t_float_values(float_val1,float_val2)" " = 1" |
a0b3c4fd | 207 | setup_xfail "mn10300-*-*" |
daf3f280 | 208 | gdb_test "p t_float_values(3.14159,float_val2)" " = 1" |
a0b3c4fd | 209 | setup_xfail "mn10300-*-*" |
daf3f280 JM |
210 | gdb_test "p t_float_values(float_val1,-2.3765)" " = 1" |
211 | ||
212 | # Test passing of arguments which might not be widened. | |
213 | gdb_test "p t_float_values2(0.0,0.0)" " = 0" | |
214 | ||
215 | # Although PR 5318 mentions SunOS specifically, this seems | |
216 | # to be a generic problem on quite a few platforms. | |
217 | if $prototypes then { | |
218 | setup_xfail "sparc-*-*" "mips*-*-*" 5318 | |
219 | if {!$gcc_compiled} then { | |
220 | setup_xfail "alpha-dec-osf2*" "i*86-*-sysv4*" 5318 | |
221 | } | |
222 | } | |
223 | gdb_test "p t_float_values2(3.14159,float_val2)" " = 1" | |
224 | gdb_test "p t_small_values(1,2,3,4,5,6,7,8,9,10)" " = 55" | |
225 | ||
226 | gdb_test "p t_double_values(0.0,0.0)" " = 0" | |
227 | gdb_test "p t_double_values(45.654,-67.66)" " = 1" | |
228 | gdb_test "p t_double_values(double_val1,double_val2)" " = 1" | |
229 | gdb_test "p t_double_values(45.654,double_val2)" " = 1" | |
230 | gdb_test "p t_double_values(double_val1,-67.66)" " = 1" | |
231 | ||
232 | } | |
233 | ||
234 | gdb_test "p t_string_values(string_val2,string_val1)" " = 0" | |
235 | gdb_test "p t_string_values(string_val1,string_val2)" " = 1" | |
236 | gdb_test "p t_string_values(\"string 1\",\"string 2\")" " = 1" | |
237 | gdb_test "p t_string_values(\"string 1\",string_val2)" " = 1" | |
238 | gdb_test "p t_string_values(string_val1,\"string 2\")" " = 1" | |
239 | ||
240 | gdb_test "p t_char_array_values(char_array_val2,char_array_val1)" " = 0" | |
241 | gdb_test "p t_char_array_values(char_array_val1,char_array_val2)" " = 1" | |
242 | gdb_test "p t_char_array_values(\"carray 1\",\"carray 2\")" " = 1" | |
243 | gdb_test "p t_char_array_values(\"carray 1\",char_array_val2)" " = 1" | |
244 | gdb_test "p t_char_array_values(char_array_val1,\"carray 2\")" " = 1" | |
245 | ||
246 | gdb_test "p doubleit(4)" " = 8" | |
247 | gdb_test "p add(4,5)" " = 9" | |
248 | gdb_test "p t_func_values(func_val2,func_val1)" " = 0" | |
249 | gdb_test "p t_func_values(func_val1,func_val2)" " = 1" | |
250 | ||
251 | # On the rs6000, we need to pass the address of the trampoline routine, | |
252 | # not the address of add itself. I don't know how to go from add to | |
253 | # the address of the trampoline. Similar problems exist on the HPPA, | |
254 | # and in fact can present an unsolvable problem as the stubs may not | |
255 | # even exist in the user's program. We've slightly recoded t_func_values | |
256 | # to avoid such problems in the common case. This may or may not help | |
257 | # the RS6000. | |
258 | setup_xfail "rs6000*-*-*" | |
daf3f280 | 259 | |
a0b3c4fd | 260 | if {![istarget hppa*-*-hpux*]} then { |
daf3f280 JM |
261 | gdb_test "p t_func_values(add,func_val2)" " = 1" |
262 | } | |
263 | ||
264 | setup_xfail "rs6000*-*-*" | |
daf3f280 | 265 | |
a0b3c4fd | 266 | if {![istarget hppa*-*-hpux*]} then { |
daf3f280 JM |
267 | gdb_test "p t_func_values(func_val1,doubleit)" " = 1" |
268 | } | |
269 | ||
270 | gdb_test "p t_call_add(func_val1,3,4)" " = 7" | |
271 | ||
272 | setup_xfail "rs6000*-*-*" | |
daf3f280 | 273 | |
a0b3c4fd | 274 | if {![istarget hppa*-*-hpux*]} then { |
daf3f280 JM |
275 | gdb_test "p t_call_add(add,3,4)" " = 7" |
276 | } | |
277 | ||
278 | gdb_test "p t_enum_value1(enumval1)" " = 1" | |
279 | gdb_test "p t_enum_value1(enum_val1)" " = 1" | |
280 | gdb_test "p t_enum_value1(enum_val2)" " = 0" | |
281 | ||
282 | gdb_test "p t_enum_value2(enumval2)" " = 1" | |
283 | gdb_test "p t_enum_value2(enum_val2)" " = 1" | |
284 | gdb_test "p t_enum_value2(enum_val1)" " = 0" | |
285 | ||
286 | gdb_test "p sum_args(1,{2})" " = 2" | |
287 | gdb_test "p sum_args(2,{2,3})" " = 5" | |
288 | gdb_test "p sum_args(3,{2,3,4})" " = 9" | |
289 | gdb_test "p sum_args(4,{2,3,4,5})" " = 14" | |
290 | gdb_test "p sum10 (1, 2, 3, 4, 5, 6, 7, 8, 9, 10)" " = 55" | |
291 | ||
292 | gdb_test "p t_structs_c(struct_val1)" "= 120 'x'" \ | |
293 | "call inferior func with struct - returns char" | |
294 | gdb_test "p t_structs_s(struct_val1)" "= 87" \ | |
295 | "call inferior func with struct - returns short" | |
296 | gdb_test "p t_structs_i(struct_val1)" "= 76" \ | |
297 | "call inferior func with struct - returns int" | |
298 | gdb_test "p t_structs_l(struct_val1)" "= 51" \ | |
299 | "call inferior func with struct - returns long" | |
daf3f280 JM |
300 | gdb_test "p t_structs_f(struct_val1)" "= 2.12.*" \ |
301 | "call inferior func with struct - returns float" | |
daf3f280 JM |
302 | gdb_test "p t_structs_d(struct_val1)" "= 9.87.*" \ |
303 | "call inferior func with struct - returns double" | |
304 | gdb_test "p t_structs_a(struct_val1)" "= (.unsigned char .. )?\"foo\"" \ | |
305 | "call inferior func with struct - returns char *" | |
306 | ||
307 | } | |
308 | ||
309 | # Start with a fresh gdb. | |
310 | ||
311 | gdb_exit | |
312 | gdb_start | |
313 | gdb_reinitialize_dir $srcdir/$subdir | |
314 | gdb_load ${binfile} | |
315 | ||
316 | gdb_test "set print sevenbit-strings" "" | |
317 | gdb_test "set print address off" "" | |
318 | gdb_test "set width 0" "" | |
319 | ||
320 | if { $hp_aCC_compiler } { | |
321 | # Do not set language explicitly to 'C'. This will cause aCC | |
322 | # tests to fail because promotion rules are different. Just let | |
323 | # the language be set to the default. | |
324 | ||
325 | if { ![runto_main] } { | |
326 | gdb_suppress_tests; | |
327 | } | |
328 | ||
329 | gdb_test "set overload-resolution 0" ".*" | |
330 | } else { | |
331 | if { ![set_lang_c] } { | |
332 | gdb_suppress_tests; | |
333 | } else { | |
334 | if { ![runto_main] } { | |
335 | gdb_suppress_tests; | |
336 | } | |
337 | } | |
338 | } | |
339 | ||
340 | gdb_test "next" ".*" | |
341 | do_function_calls | |
342 | ||
343 | return 0 |