]> git.ipfire.org Git - thirdparty/binutils-gdb.git/blame - gdb/infcall.c
2003-09-08 Andrew Cagney <cagney@redhat.com>
[thirdparty/binutils-gdb.git] / gdb / infcall.c
CommitLineData
04714b91
AC
1/* Perform an inferior function call, for GDB, the GNU debugger.
2
3 Copyright 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994,
4 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 Free Software
5 Foundation, Inc.
6
7 This file is part of GDB.
8
9 This program is free software; you can redistribute it and/or modify
10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation; either version 2 of the License, or
12 (at your option) any later version.
13
14 This program is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 GNU General Public License for more details.
18
19 You should have received a copy of the GNU General Public License
20 along with this program; if not, write to the Free Software
21 Foundation, Inc., 59 Temple Place - Suite 330,
22 Boston, MA 02111-1307, USA. */
23
24#include "defs.h"
25#include "breakpoint.h"
26#include "target.h"
27#include "regcache.h"
28#include "inferior.h"
29#include "gdb_assert.h"
30#include "block.h"
31#include "gdbcore.h"
32#include "language.h"
33#include "symfile.h"
34#include "gdbcmd.h"
35#include "command.h"
36#include "gdb_string.h"
b9362cc7 37#include "infcall.h"
04714b91
AC
38
39/* NOTE: cagney/2003-04-16: What's the future of this code?
40
41 GDB needs an asynchronous expression evaluator, that means an
42 asynchronous inferior function call implementation, and that in
43 turn means restructuring the code so that it is event driven. */
44
45/* How you should pass arguments to a function depends on whether it
46 was defined in K&R style or prototype style. If you define a
47 function using the K&R syntax that takes a `float' argument, then
48 callers must pass that argument as a `double'. If you define the
49 function using the prototype syntax, then you must pass the
50 argument as a `float', with no promotion.
51
52 Unfortunately, on certain older platforms, the debug info doesn't
53 indicate reliably how each function was defined. A function type's
54 TYPE_FLAG_PROTOTYPED flag may be clear, even if the function was
55 defined in prototype style. When calling a function whose
56 TYPE_FLAG_PROTOTYPED flag is clear, GDB consults this flag to
57 decide what to do.
58
59 For modern targets, it is proper to assume that, if the prototype
60 flag is clear, that can be trusted: `float' arguments should be
61 promoted to `double'. For some older targets, if the prototype
62 flag is clear, that doesn't tell us anything. The default is to
63 trust the debug information; the user can override this behavior
64 with "set coerce-float-to-double 0". */
65
66static int coerce_float_to_double_p = 1;
67
68/* This boolean tells what gdb should do if a signal is received while
69 in a function called from gdb (call dummy). If set, gdb unwinds
70 the stack and restore the context to what as it was before the
71 call.
72
73 The default is to stop in the frame where the signal was received. */
74
75int unwind_on_signal_p = 0;
76
77/* Perform the standard coercions that are specified
78 for arguments to be passed to C functions.
79
80 If PARAM_TYPE is non-NULL, it is the expected parameter type.
81 IS_PROTOTYPED is non-zero if the function declaration is prototyped. */
82
83static struct value *
84value_arg_coerce (struct value *arg, struct type *param_type,
85 int is_prototyped)
86{
87 register struct type *arg_type = check_typedef (VALUE_TYPE (arg));
88 register struct type *type
89 = param_type ? check_typedef (param_type) : arg_type;
90
91 switch (TYPE_CODE (type))
92 {
93 case TYPE_CODE_REF:
94 if (TYPE_CODE (arg_type) != TYPE_CODE_REF
95 && TYPE_CODE (arg_type) != TYPE_CODE_PTR)
96 {
97 arg = value_addr (arg);
98 VALUE_TYPE (arg) = param_type;
99 return arg;
100 }
101 break;
102 case TYPE_CODE_INT:
103 case TYPE_CODE_CHAR:
104 case TYPE_CODE_BOOL:
105 case TYPE_CODE_ENUM:
106 /* If we don't have a prototype, coerce to integer type if necessary. */
107 if (!is_prototyped)
108 {
109 if (TYPE_LENGTH (type) < TYPE_LENGTH (builtin_type_int))
110 type = builtin_type_int;
111 }
112 /* Currently all target ABIs require at least the width of an integer
113 type for an argument. We may have to conditionalize the following
114 type coercion for future targets. */
115 if (TYPE_LENGTH (type) < TYPE_LENGTH (builtin_type_int))
116 type = builtin_type_int;
117 break;
118 case TYPE_CODE_FLT:
119 if (!is_prototyped && coerce_float_to_double_p)
120 {
121 if (TYPE_LENGTH (type) < TYPE_LENGTH (builtin_type_double))
122 type = builtin_type_double;
123 else if (TYPE_LENGTH (type) > TYPE_LENGTH (builtin_type_double))
124 type = builtin_type_long_double;
125 }
126 break;
127 case TYPE_CODE_FUNC:
128 type = lookup_pointer_type (type);
129 break;
130 case TYPE_CODE_ARRAY:
131 /* Arrays are coerced to pointers to their first element, unless
132 they are vectors, in which case we want to leave them alone,
133 because they are passed by value. */
134 if (current_language->c_style_arrays)
135 if (!TYPE_VECTOR (type))
136 type = lookup_pointer_type (TYPE_TARGET_TYPE (type));
137 break;
138 case TYPE_CODE_UNDEF:
139 case TYPE_CODE_PTR:
140 case TYPE_CODE_STRUCT:
141 case TYPE_CODE_UNION:
142 case TYPE_CODE_VOID:
143 case TYPE_CODE_SET:
144 case TYPE_CODE_RANGE:
145 case TYPE_CODE_STRING:
146 case TYPE_CODE_BITSTRING:
147 case TYPE_CODE_ERROR:
148 case TYPE_CODE_MEMBER:
149 case TYPE_CODE_METHOD:
150 case TYPE_CODE_COMPLEX:
151 default:
152 break;
153 }
154
155 return value_cast (type, arg);
156}
157
158/* Determine a function's address and its return type from its value.
159 Calls error() if the function is not valid for calling. */
160
a9fa03de 161CORE_ADDR
04714b91
AC
162find_function_addr (struct value *function, struct type **retval_type)
163{
164 register struct type *ftype = check_typedef (VALUE_TYPE (function));
165 register enum type_code code = TYPE_CODE (ftype);
166 struct type *value_type;
167 CORE_ADDR funaddr;
168
169 /* If it's a member function, just look at the function
170 part of it. */
171
172 /* Determine address to call. */
173 if (code == TYPE_CODE_FUNC || code == TYPE_CODE_METHOD)
174 {
175 funaddr = VALUE_ADDRESS (function);
176 value_type = TYPE_TARGET_TYPE (ftype);
177 }
178 else if (code == TYPE_CODE_PTR)
179 {
180 funaddr = value_as_address (function);
181 ftype = check_typedef (TYPE_TARGET_TYPE (ftype));
182 if (TYPE_CODE (ftype) == TYPE_CODE_FUNC
183 || TYPE_CODE (ftype) == TYPE_CODE_METHOD)
184 {
185 funaddr = CONVERT_FROM_FUNC_PTR_ADDR (funaddr);
186 value_type = TYPE_TARGET_TYPE (ftype);
187 }
188 else
189 value_type = builtin_type_int;
190 }
191 else if (code == TYPE_CODE_INT)
192 {
193 /* Handle the case of functions lacking debugging info.
194 Their values are characters since their addresses are char */
195 if (TYPE_LENGTH (ftype) == 1)
196 funaddr = value_as_address (value_addr (function));
197 else
198 /* Handle integer used as address of a function. */
199 funaddr = (CORE_ADDR) value_as_long (function);
200
201 value_type = builtin_type_int;
202 }
203 else
204 error ("Invalid data type for function to be called.");
205
206 *retval_type = value_type;
207 return funaddr;
208}
209
210/* Call breakpoint_auto_delete on the current contents of the bpstat
211 pointed to by arg (which is really a bpstat *). */
212
213static void
214breakpoint_auto_delete_contents (void *arg)
215{
216 breakpoint_auto_delete (*(bpstat *) arg);
217}
218
7043d8dc
AC
219static CORE_ADDR
220legacy_push_dummy_code (struct gdbarch *gdbarch,
221 CORE_ADDR sp, CORE_ADDR funaddr, int using_gcc,
222 struct value **args, int nargs,
223 struct type *value_type,
224 CORE_ADDR *real_pc, CORE_ADDR *bp_addr)
225{
b1e29e33
AC
226 /* CALL_DUMMY is an array of words (DEPRECATED_REGISTER_SIZE), but
227 each word is in host byte order. Before calling
228 DEPRECATED_FIX_CALL_DUMMY, we byteswap it and remove any extra
229 bytes which might exist because ULONGEST is bigger than
230 DEPRECATED_REGISTER_SIZE. */
7043d8dc
AC
231 /* NOTE: This is pretty wierd, as the call dummy is actually a
232 sequence of instructions. But CISC machines will have to pack
b1e29e33
AC
233 the instructions into DEPRECATED_REGISTER_SIZE units (and so will
234 RISC machines for which INSTRUCTION_SIZE is not
235 DEPRECATED_REGISTER_SIZE). */
7043d8dc
AC
236 /* NOTE: This is pretty stupid. CALL_DUMMY should be in strict
237 target byte order. */
238 CORE_ADDR start_sp;
b1e29e33
AC
239 ULONGEST *dummy = alloca (DEPRECATED_SIZEOF_CALL_DUMMY_WORDS);
240 int sizeof_dummy1 = (DEPRECATED_REGISTER_SIZE
241 * DEPRECATED_SIZEOF_CALL_DUMMY_WORDS
7043d8dc
AC
242 / sizeof (ULONGEST));
243 char *dummy1 = alloca (sizeof_dummy1);
b1e29e33
AC
244 memcpy (dummy, DEPRECATED_CALL_DUMMY_WORDS,
245 DEPRECATED_SIZEOF_CALL_DUMMY_WORDS);
7043d8dc
AC
246 if (INNER_THAN (1, 2))
247 {
248 /* Stack grows down */
249 sp -= sizeof_dummy1;
250 start_sp = sp;
251 }
252 else
253 {
254 /* Stack grows up */
255 start_sp = sp;
256 sp += sizeof_dummy1;
257 }
258 /* NOTE: cagney/2002-09-10: Don't bother re-adjusting the stack
259 after allocating space for the call dummy. A target can specify
b1e29e33
AC
260 a SIZEOF_DUMMY1 (via DEPRECATED_SIZEOF_CALL_DUMMY_WORDS) such
261 that all local alignment requirements are met. */
7043d8dc
AC
262 /* Create a call sequence customized for this function and the
263 number of arguments for it. */
264 {
265 int i;
b1e29e33 266 for (i = 0; i < (int) (DEPRECATED_SIZEOF_CALL_DUMMY_WORDS / sizeof (dummy[0]));
7043d8dc 267 i++)
b1e29e33
AC
268 store_unsigned_integer (&dummy1[i * DEPRECATED_REGISTER_SIZE],
269 DEPRECATED_REGISTER_SIZE,
7043d8dc
AC
270 (ULONGEST) dummy[i]);
271 }
272 /* NOTE: cagney/2003-04-22: This computation of REAL_PC, BP_ADDR and
273 DUMMY_ADDR is pretty messed up. It comes from constant tinkering
b1e29e33 274 with the values. Instead a DEPRECATED_FIX_CALL_DUMMY replacement
7043d8dc
AC
275 (PUSH_DUMMY_BREAKPOINT?) should just do everything. */
276#ifdef GDB_TARGET_IS_HPPA
222e5d1d
AC
277 (*real_pc) = DEPRECATED_FIX_CALL_DUMMY (dummy1, start_sp, funaddr, nargs,
278 args, value_type, using_gcc);
7043d8dc 279#else
b1e29e33 280 if (DEPRECATED_FIX_CALL_DUMMY_P ())
7043d8dc
AC
281 {
282 /* gdb_assert (CALL_DUMMY_LOCATION == ON_STACK) true? */
b1e29e33
AC
283 DEPRECATED_FIX_CALL_DUMMY (dummy1, start_sp, funaddr, nargs, args,
284 value_type, using_gcc);
7043d8dc
AC
285 }
286 (*real_pc) = start_sp;
287#endif
288 /* Yes, the offset is applied to the real_pc and not the dummy addr.
289 Ulgh! Blame the HP/UX target. */
b1e29e33 290 (*bp_addr) = (*real_pc) + DEPRECATED_CALL_DUMMY_BREAKPOINT_OFFSET;
7043d8dc
AC
291 /* Yes, the offset is applied to the real_pc and not the
292 dummy_addr. Ulgh! Blame the HP/UX target. */
b1e29e33 293 (*real_pc) += DEPRECATED_CALL_DUMMY_START_OFFSET;
7043d8dc
AC
294 write_memory (start_sp, (char *) dummy1, sizeof_dummy1);
295 if (DEPRECATED_USE_GENERIC_DUMMY_FRAMES)
296 generic_save_call_dummy_addr (start_sp, start_sp + sizeof_dummy1);
297 return sp;
298}
299
300static CORE_ADDR
301generic_push_dummy_code (struct gdbarch *gdbarch,
302 CORE_ADDR sp, CORE_ADDR funaddr, int using_gcc,
303 struct value **args, int nargs,
304 struct type *value_type,
305 CORE_ADDR *real_pc, CORE_ADDR *bp_addr)
306{
307 /* Something here to findout the size of a breakpoint and then
308 allocate space for it on the stack. */
309 int bplen;
310 /* This code assumes frame align. */
311 gdb_assert (gdbarch_frame_align_p (gdbarch));
312 /* Force the stack's alignment. The intent is to ensure that the SP
313 is aligned to at least a breakpoint instruction's boundary. */
314 sp = gdbarch_frame_align (gdbarch, sp);
315 /* Allocate space for, and then position the breakpoint on the
316 stack. */
317 if (gdbarch_inner_than (gdbarch, 1, 2))
318 {
319 CORE_ADDR bppc = sp;
320 gdbarch_breakpoint_from_pc (gdbarch, &bppc, &bplen);
321 sp = gdbarch_frame_align (gdbarch, sp - bplen);
322 (*bp_addr) = sp;
323 /* Should the breakpoint size/location be re-computed here? */
324 }
325 else
326 {
327 (*bp_addr) = sp;
328 gdbarch_breakpoint_from_pc (gdbarch, bp_addr, &bplen);
329 sp = gdbarch_frame_align (gdbarch, sp + bplen);
330 }
331 /* Inferior resumes at the function entry point. */
332 (*real_pc) = funaddr;
333 return sp;
334}
335
b1e29e33
AC
336/* Provide backward compatibility. Once DEPRECATED_FIX_CALL_DUMMY is
337 eliminated, this can be simplified. */
7043d8dc
AC
338
339static CORE_ADDR
340push_dummy_code (struct gdbarch *gdbarch,
341 CORE_ADDR sp, CORE_ADDR funaddr, int using_gcc,
342 struct value **args, int nargs,
343 struct type *value_type,
344 CORE_ADDR *real_pc, CORE_ADDR *bp_addr)
345{
346 if (gdbarch_push_dummy_code_p (gdbarch))
347 return gdbarch_push_dummy_code (gdbarch, sp, funaddr, using_gcc,
348 args, nargs, value_type, real_pc, bp_addr);
b1e29e33 349 else if (DEPRECATED_FIX_CALL_DUMMY_P ())
7043d8dc
AC
350 return legacy_push_dummy_code (gdbarch, sp, funaddr, using_gcc,
351 args, nargs, value_type, real_pc, bp_addr);
352 else
353 return generic_push_dummy_code (gdbarch, sp, funaddr, using_gcc,
354 args, nargs, value_type, real_pc, bp_addr);
355}
356
04714b91
AC
357/* All this stuff with a dummy frame may seem unnecessarily complicated
358 (why not just save registers in GDB?). The purpose of pushing a dummy
359 frame which looks just like a real frame is so that if you call a
360 function and then hit a breakpoint (get a signal, etc), "backtrace"
361 will look right. Whether the backtrace needs to actually show the
362 stack at the time the inferior function was called is debatable, but
363 it certainly needs to not display garbage. So if you are contemplating
364 making dummy frames be different from normal frames, consider that. */
365
366/* Perform a function call in the inferior.
367 ARGS is a vector of values of arguments (NARGS of them).
368 FUNCTION is a value, the function to be called.
369 Returns a value representing what the function returned.
370 May fail to return, if a breakpoint or signal is hit
371 during the execution of the function.
372
373 ARGS is modified to contain coerced values. */
374
375struct value *
376call_function_by_hand (struct value *function, int nargs, struct value **args)
377{
378 register CORE_ADDR sp;
04714b91 379 CORE_ADDR dummy_addr;
04714b91
AC
380 struct type *value_type;
381 unsigned char struct_return;
382 CORE_ADDR struct_addr = 0;
383 struct regcache *retbuf;
384 struct cleanup *retbuf_cleanup;
385 struct inferior_status *inf_status;
386 struct cleanup *inf_status_cleanup;
387 CORE_ADDR funaddr;
388 int using_gcc; /* Set to version of gcc in use, or zero if not gcc */
389 CORE_ADDR real_pc;
04714b91 390 struct type *ftype = check_typedef (SYMBOL_TYPE (function));
d585e13a 391 CORE_ADDR bp_addr;
04714b91 392
04714b91
AC
393 if (!target_has_execution)
394 noprocess ();
395
396 /* Create a cleanup chain that contains the retbuf (buffer
397 containing the register values). This chain is create BEFORE the
398 inf_status chain so that the inferior status can cleaned up
399 (restored or discarded) without having the retbuf freed. */
400 retbuf = regcache_xmalloc (current_gdbarch);
401 retbuf_cleanup = make_cleanup_regcache_xfree (retbuf);
402
403 /* A cleanup for the inferior status. Create this AFTER the retbuf
404 so that this can be discarded or applied without interfering with
405 the regbuf. */
406 inf_status = save_inferior_status (1);
407 inf_status_cleanup = make_cleanup_restore_inferior_status (inf_status);
408
409 if (DEPRECATED_PUSH_DUMMY_FRAME_P ())
410 {
411 /* DEPRECATED_PUSH_DUMMY_FRAME is responsible for saving the
412 inferior registers (and frame_pop() for restoring them). (At
413 least on most machines) they are saved on the stack in the
414 inferior. */
415 DEPRECATED_PUSH_DUMMY_FRAME;
416 }
417 else
418 {
419 /* FIXME: cagney/2003-02-26: Step zero of this little tinker is
420 to extract the generic dummy frame code from the architecture
421 vector. Hence this direct call.
422
423 A follow-on change is to modify this interface so that it takes
c48a845b 424 thread OR frame OR ptid as a parameter, and returns a dummy
04714b91 425 frame handle. The handle can then be used further down as a
a59fe496
AC
426 parameter to generic_save_dummy_frame_tos(). Hmm, thinking
427 about it, since everything is ment to be using generic dummy
428 frames, why not even use some of the dummy frame code to here -
429 do a regcache dup and then pass the duped regcache, along with
430 all the other stuff, at one single point.
04714b91
AC
431
432 In fact, you can even save the structure's return address in the
433 dummy frame and fix one of those nasty lost struct return edge
434 conditions. */
435 generic_push_dummy_frame ();
436 }
437
04714b91 438 /* Ensure that the initial SP is correctly aligned. */
ebc7896c
AC
439 {
440 CORE_ADDR old_sp = read_sp ();
441 if (gdbarch_frame_align_p (current_gdbarch))
442 {
8b148df9
AC
443 sp = gdbarch_frame_align (current_gdbarch, old_sp);
444 /* NOTE: cagney/2003-08-13: Skip the "red zone". For some
445 ABIs, a function can use memory beyond the inner most stack
446 address. AMD64 called that region the "red zone". Skip at
447 least the "red zone" size before allocating any space on
448 the stack. */
449 if (INNER_THAN (1, 2))
450 sp -= gdbarch_frame_red_zone_size (current_gdbarch);
451 else
452 sp += gdbarch_frame_red_zone_size (current_gdbarch);
453 /* Still aligned? */
454 gdb_assert (sp == gdbarch_frame_align (current_gdbarch, sp));
ebc7896c
AC
455 /* NOTE: cagney/2002-09-18:
456
457 On a RISC architecture, a void parameterless generic dummy
458 frame (i.e., no parameters, no result) typically does not
459 need to push anything the stack and hence can leave SP and
c48a845b 460 FP. Similarly, a frameless (possibly leaf) function does
ebc7896c
AC
461 not push anything on the stack and, hence, that too can
462 leave FP and SP unchanged. As a consequence, a sequence of
463 void parameterless generic dummy frame calls to frameless
464 functions will create a sequence of effectively identical
465 frames (SP, FP and TOS and PC the same). This, not
466 suprisingly, results in what appears to be a stack in an
467 infinite loop --- when GDB tries to find a generic dummy
468 frame on the internal dummy frame stack, it will always
469 find the first one.
470
471 To avoid this problem, the code below always grows the
472 stack. That way, two dummy frames can never be identical.
473 It does burn a few bytes of stack but that is a small price
474 to pay :-). */
ebc7896c
AC
475 if (sp == old_sp)
476 {
477 if (INNER_THAN (1, 2))
478 /* Stack grows down. */
479 sp = gdbarch_frame_align (current_gdbarch, old_sp - 1);
480 else
481 /* Stack grows up. */
482 sp = gdbarch_frame_align (current_gdbarch, old_sp + 1);
483 }
484 gdb_assert ((INNER_THAN (1, 2) && sp <= old_sp)
485 || (INNER_THAN (2, 1) && sp >= old_sp));
486 }
487 else
a59fe496
AC
488 /* FIXME: cagney/2002-09-18: Hey, you loose!
489
8b148df9
AC
490 Who knows how badly aligned the SP is!
491
492 If the generic dummy frame ends up empty (because nothing is
493 pushed) GDB won't be able to correctly perform back traces.
494 If a target is having trouble with backtraces, first thing to
495 do is add FRAME_ALIGN() to the architecture vector. If that
496 fails, try unwind_dummy_id().
497
498 If the ABI specifies a "Red Zone" (see the doco) the code
499 below will quietly trash it. */
ebc7896c
AC
500 sp = old_sp;
501 }
04714b91 502
04714b91
AC
503 funaddr = find_function_addr (function, &value_type);
504 CHECK_TYPEDEF (value_type);
505
506 {
507 struct block *b = block_for_pc (funaddr);
508 /* If compiled without -g, assume GCC 2. */
509 using_gcc = (b == NULL ? 2 : BLOCK_GCC_COMPILED (b));
510 }
511
512 /* Are we returning a value using a structure return or a normal
513 value return? */
514
515 struct_return = using_struct_return (function, funaddr, value_type,
516 using_gcc);
517
7043d8dc
AC
518 /* Determine the location of the breakpoint (and possibly other
519 stuff) that the called function will return to. The SPARC, for a
520 function returning a structure or union, needs to make space for
521 not just the breakpoint but also an extra word containing the
522 size (?) of the structure being passed. */
523
524 /* The actual breakpoint (at BP_ADDR) is inserted separatly so there
525 is no need to write that out. */
526
04714b91
AC
527 switch (CALL_DUMMY_LOCATION)
528 {
529 case ON_STACK:
7043d8dc
AC
530 /* "dummy_addr" is here just to keep old targets happy. New
531 targets return that same information via "sp" and "bp_addr". */
532 if (INNER_THAN (1, 2))
d585e13a 533 {
7043d8dc
AC
534 sp = push_dummy_code (current_gdbarch, sp, funaddr,
535 using_gcc, args, nargs, value_type,
536 &real_pc, &bp_addr);
537 dummy_addr = sp;
d585e13a 538 }
7043d8dc
AC
539 else
540 {
541 dummy_addr = sp;
542 sp = push_dummy_code (current_gdbarch, sp, funaddr,
543 using_gcc, args, nargs, value_type,
544 &real_pc, &bp_addr);
545 }
546 break;
04714b91 547 case AT_ENTRY_POINT:
c89b70f1
AC
548 if (DEPRECATED_FIX_CALL_DUMMY_P ())
549 {
550 /* Sigh. Some targets use DEPRECATED_FIX_CALL_DUMMY to
551 shove extra stuff onto the stack or into registers. That
552 code should be in PUSH_DUMMY_CALL, however, in the mean
553 time ... */
554 /* If the target is manipulating DUMMY1, it looses big time. */
555 void *dummy1 = NULL;
556 DEPRECATED_FIX_CALL_DUMMY (dummy1, sp, funaddr, nargs, args,
557 value_type, using_gcc);
558 }
04714b91
AC
559 real_pc = funaddr;
560 dummy_addr = CALL_DUMMY_ADDRESS ();
0285512f
AC
561 /* Make certain that the address points at real code, and not a
562 function descriptor. */
563 dummy_addr = CONVERT_FROM_FUNC_PTR_ADDR (dummy_addr);
d585e13a
AC
564 /* A call dummy always consists of just a single breakpoint, so
565 it's address is the same as the address of the dummy. */
566 bp_addr = dummy_addr;
04714b91 567 break;
9710e734
AC
568 case AT_SYMBOL:
569 /* Some executables define a symbol __CALL_DUMMY_ADDRESS whose
570 address is the location where the breakpoint should be
571 placed. Once all targets are using the overhauled frame code
572 this can be deleted - ON_STACK is a better option. */
573 {
574 struct minimal_symbol *sym;
575
576 sym = lookup_minimal_symbol ("__CALL_DUMMY_ADDRESS", NULL, NULL);
577 real_pc = funaddr;
578 if (sym)
579 dummy_addr = SYMBOL_VALUE_ADDRESS (sym);
580 else
581 dummy_addr = entry_point_address ();
0285512f
AC
582 /* Make certain that the address points at real code, and not
583 a function descriptor. */
584 dummy_addr = CONVERT_FROM_FUNC_PTR_ADDR (dummy_addr);
585 /* A call dummy always consists of just a single breakpoint,
586 so it's address is the same as the address of the dummy. */
9710e734
AC
587 bp_addr = dummy_addr;
588 break;
589 }
04714b91
AC
590 default:
591 internal_error (__FILE__, __LINE__, "bad switch");
592 }
593
7043d8dc
AC
594 if (DEPRECATED_USE_GENERIC_DUMMY_FRAMES)
595 /* Save where the breakpoint is going to be inserted so that the
596 dummy-frame code is later able to re-identify it. */
597 generic_save_call_dummy_addr (bp_addr, bp_addr + 1);
598
04714b91
AC
599 if (nargs < TYPE_NFIELDS (ftype))
600 error ("too few arguments in function call");
601
ebc7896c
AC
602 {
603 int i;
604 for (i = nargs - 1; i >= 0; i--)
605 {
606 int prototyped;
607 struct type *param_type;
608
609 /* FIXME drow/2002-05-31: Should just always mark methods as
610 prototyped. Can we respect TYPE_VARARGS? Probably not. */
611 if (TYPE_CODE (ftype) == TYPE_CODE_METHOD)
612 prototyped = 1;
613 else if (i < TYPE_NFIELDS (ftype))
614 prototyped = TYPE_PROTOTYPED (ftype);
615 else
616 prototyped = 0;
617
618 if (i < TYPE_NFIELDS (ftype))
619 param_type = TYPE_FIELD_TYPE (ftype, i);
620 else
621 param_type = NULL;
622
623 args[i] = value_arg_coerce (args[i], param_type, prototyped);
624
625 /* elz: this code is to handle the case in which the function
626 to be called has a pointer to function as parameter and the
627 corresponding actual argument is the address of a function
628 and not a pointer to function variable. In aCC compiled
629 code, the calls through pointers to functions (in the body
630 of the function called by hand) are made via
631 $$dyncall_external which requires some registers setting,
632 this is taken care of if we call via a function pointer
633 variable, but not via a function address. In cc this is
634 not a problem. */
635
636 if (using_gcc == 0)
637 {
638 if (param_type != NULL && TYPE_CODE (ftype) != TYPE_CODE_METHOD)
639 {
640 /* if this parameter is a pointer to function. */
641 if (TYPE_CODE (param_type) == TYPE_CODE_PTR)
642 if (TYPE_CODE (TYPE_TARGET_TYPE (param_type)) == TYPE_CODE_FUNC)
643 /* elz: FIXME here should go the test about the
644 compiler used to compile the target. We want to
645 issue the error message only if the compiler
646 used was HP's aCC. If we used HP's cc, then
647 there is no problem and no need to return at
648 this point. */
649 /* Go see if the actual parameter is a variable of
650 type pointer to function or just a function. */
651 if (args[i]->lval == not_lval)
652 {
653 char *arg_name;
654 if (find_pc_partial_function ((CORE_ADDR) args[i]->aligner.contents[0], &arg_name, NULL, NULL))
655 error ("\
04714b91
AC
656You cannot use function <%s> as argument. \n\
657You must use a pointer to function type variable. Command ignored.", arg_name);
ebc7896c
AC
658 }
659 }
660 }
661 }
662 }
04714b91
AC
663
664 if (REG_STRUCT_HAS_ADDR_P ())
665 {
ebc7896c 666 int i;
04714b91
AC
667 /* This is a machine like the sparc, where we may need to pass a
668 pointer to the structure, not the structure itself. */
669 for (i = nargs - 1; i >= 0; i--)
670 {
671 struct type *arg_type = check_typedef (VALUE_TYPE (args[i]));
672 if ((TYPE_CODE (arg_type) == TYPE_CODE_STRUCT
673 || TYPE_CODE (arg_type) == TYPE_CODE_UNION
674 || TYPE_CODE (arg_type) == TYPE_CODE_ARRAY
675 || TYPE_CODE (arg_type) == TYPE_CODE_STRING
676 || TYPE_CODE (arg_type) == TYPE_CODE_BITSTRING
677 || TYPE_CODE (arg_type) == TYPE_CODE_SET
678 || (TYPE_CODE (arg_type) == TYPE_CODE_FLT
679 && TYPE_LENGTH (arg_type) > 8)
680 )
681 && REG_STRUCT_HAS_ADDR (using_gcc, arg_type))
682 {
683 CORE_ADDR addr;
684 int len; /* = TYPE_LENGTH (arg_type); */
685 int aligned_len;
686 arg_type = check_typedef (VALUE_ENCLOSING_TYPE (args[i]));
687 len = TYPE_LENGTH (arg_type);
688
689 if (STACK_ALIGN_P ())
690 /* MVS 11/22/96: I think at least some of this
691 stack_align code is really broken. Better to let
692 PUSH_ARGUMENTS adjust the stack in a target-defined
693 manner. */
694 aligned_len = STACK_ALIGN (len);
695 else
696 aligned_len = len;
697 if (INNER_THAN (1, 2))
698 {
699 /* stack grows downward */
700 sp -= aligned_len;
701 /* ... so the address of the thing we push is the
702 stack pointer after we push it. */
703 addr = sp;
704 }
705 else
706 {
707 /* The stack grows up, so the address of the thing
708 we push is the stack pointer before we push it. */
709 addr = sp;
710 sp += aligned_len;
711 }
712 /* Push the structure. */
713 write_memory (addr, VALUE_CONTENTS_ALL (args[i]), len);
714 /* The value we're going to pass is the address of the
715 thing we just pushed. */
716 /*args[i] = value_from_longest (lookup_pointer_type (value_type),
717 (LONGEST) addr); */
718 args[i] = value_from_pointer (lookup_pointer_type (arg_type),
719 addr);
720 }
721 }
722 }
723
724
725 /* Reserve space for the return structure to be written on the
726 stack, if necessary. Make certain that the value is correctly
727 aligned. */
728
729 if (struct_return)
730 {
731 int len = TYPE_LENGTH (value_type);
732 if (STACK_ALIGN_P ())
733 /* NOTE: cagney/2003-03-22: Should rely on frame align, rather
734 than stack align to force the alignment of the stack. */
735 len = STACK_ALIGN (len);
736 if (INNER_THAN (1, 2))
737 {
738 /* Stack grows downward. Align STRUCT_ADDR and SP after
739 making space for the return value. */
740 sp -= len;
741 if (gdbarch_frame_align_p (current_gdbarch))
742 sp = gdbarch_frame_align (current_gdbarch, sp);
743 struct_addr = sp;
744 }
745 else
746 {
747 /* Stack grows upward. Align the frame, allocate space, and
748 then again, re-align the frame??? */
749 if (gdbarch_frame_align_p (current_gdbarch))
750 sp = gdbarch_frame_align (current_gdbarch, sp);
751 struct_addr = sp;
752 sp += len;
753 if (gdbarch_frame_align_p (current_gdbarch))
754 sp = gdbarch_frame_align (current_gdbarch, sp);
755 }
756 }
757
758 /* elz: on HPPA no need for this extra alignment, maybe it is needed
759 on other architectures. This is because all the alignment is
760 taken care of in the above code (ifdef REG_STRUCT_HAS_ADDR) and
761 in hppa_push_arguments */
762 /* NOTE: cagney/2003-03-24: The below code is very broken. Given an
763 odd sized parameter the below will mis-align the stack. As was
764 suggested back in '96, better to let PUSH_ARGUMENTS handle it. */
765 if (DEPRECATED_EXTRA_STACK_ALIGNMENT_NEEDED)
766 {
767 /* MVS 11/22/96: I think at least some of this stack_align code
768 is really broken. Better to let push_dummy_call() adjust the
769 stack in a target-defined manner. */
770 if (STACK_ALIGN_P () && INNER_THAN (1, 2))
771 {
772 /* If stack grows down, we must leave a hole at the top. */
773 int len = 0;
ebc7896c 774 int i;
04714b91
AC
775 for (i = nargs - 1; i >= 0; i--)
776 len += TYPE_LENGTH (VALUE_ENCLOSING_TYPE (args[i]));
777 if (DEPRECATED_CALL_DUMMY_STACK_ADJUST_P ())
778 len += DEPRECATED_CALL_DUMMY_STACK_ADJUST;
779 sp -= STACK_ALIGN (len) - len;
780 }
781 }
782
783 /* Create the dummy stack frame. Pass in the call dummy address as,
784 presumably, the ABI code knows where, in the call dummy, the
785 return address should be pointed. */
786 if (gdbarch_push_dummy_call_p (current_gdbarch))
787 /* When there is no push_dummy_call method, should this code
788 simply error out. That would the implementation of this method
789 for all ABIs (which is probably a good thing). */
6a65450a 790 sp = gdbarch_push_dummy_call (current_gdbarch, funaddr, current_regcache,
7043d8dc 791 bp_addr, nargs, args, sp, struct_return,
04714b91
AC
792 struct_addr);
793 else if (DEPRECATED_PUSH_ARGUMENTS_P ())
794 /* Keep old targets working. */
795 sp = DEPRECATED_PUSH_ARGUMENTS (nargs, args, sp, struct_return,
796 struct_addr);
797 else
798 sp = legacy_push_arguments (nargs, args, sp, struct_return, struct_addr);
799
800 if (DEPRECATED_PUSH_RETURN_ADDRESS_P ())
801 /* for targets that use no CALL_DUMMY */
802 /* There are a number of targets now which actually don't write
803 any CALL_DUMMY instructions into the target, but instead just
804 save the machine state, push the arguments, and jump directly
805 to the callee function. Since this doesn't actually involve
806 executing a JSR/BSR instruction, the return address must be set
807 up by hand, either by pushing onto the stack or copying into a
808 return-address register as appropriate. Formerly this has been
809 done in PUSH_ARGUMENTS, but that's overloading its
810 functionality a bit, so I'm making it explicit to do it here. */
d585e13a
AC
811 /* NOTE: cagney/2003-04-22: The first parameter ("real_pc") has
812 been replaced with zero, it turns out that no implementation
813 used that parameter. This occured because the value being
814 supplied - the address of the called function's entry point
815 instead of the address of the breakpoint that the called
816 function should return to - wasn't useful. */
817 sp = DEPRECATED_PUSH_RETURN_ADDRESS (0, sp);
04714b91
AC
818
819 /* NOTE: cagney/2003-03-23: Diable this code when there is a
820 push_dummy_call() method. Since that method will have already
821 handled any alignment issues, the code below is entirely
822 redundant. */
823 if (!gdbarch_push_dummy_call_p (current_gdbarch)
824 && STACK_ALIGN_P () && !INNER_THAN (1, 2))
825 {
826 /* If stack grows up, we must leave a hole at the bottom, note
827 that sp already has been advanced for the arguments! */
828 if (DEPRECATED_CALL_DUMMY_STACK_ADJUST_P ())
829 sp += DEPRECATED_CALL_DUMMY_STACK_ADJUST;
830 sp = STACK_ALIGN (sp);
831 }
832
833/* XXX This seems wrong. For stacks that grow down we shouldn't do
834 anything here! */
835 /* MVS 11/22/96: I think at least some of this stack_align code is
836 really broken. Better to let PUSH_ARGUMENTS adjust the stack in
837 a target-defined manner. */
838 if (DEPRECATED_CALL_DUMMY_STACK_ADJUST_P ())
839 if (INNER_THAN (1, 2))
840 {
841 /* stack grows downward */
842 sp -= DEPRECATED_CALL_DUMMY_STACK_ADJUST;
843 }
844
845 /* Store the address at which the structure is supposed to be
846 written. */
847 /* NOTE: 2003-03-24: Since PUSH_ARGUMENTS can (and typically does)
848 store the struct return address, this call is entirely redundant. */
849 if (struct_return && DEPRECATED_STORE_STRUCT_RETURN_P ())
850 DEPRECATED_STORE_STRUCT_RETURN (struct_addr, sp);
851
1fd4ae22
AC
852 /* Write the stack pointer. This is here because the statements
853 above might fool with it. On SPARC, this write also stores the
854 register window into the right place in the new stack frame,
855 which otherwise wouldn't happen (see store_inferior_registers in
856 sparc-nat.c). */
857 /* NOTE: cagney/2003-03-23: Since the architecture method
858 push_dummy_call() should have already stored the stack pointer
859 (as part of creating the fake call frame), and none of the code
860 following that call adjusts the stack-pointer value, the below
861 call is entirely redundant. */
04714b91
AC
862 if (DEPRECATED_DUMMY_WRITE_SP_P ())
863 DEPRECATED_DUMMY_WRITE_SP (sp);
864
3e210248
AC
865 if (gdbarch_unwind_dummy_id_p (current_gdbarch))
866 {
867 /* Sanity. The exact same SP value is returned by
868 PUSH_DUMMY_CALL, saved as the dummy-frame TOS, and used by
869 unwind_dummy_id to form the frame ID's stack address. */
870 gdb_assert (DEPRECATED_USE_GENERIC_DUMMY_FRAMES);
871 generic_save_dummy_frame_tos (sp);
872 }
a59fe496
AC
873 else if (DEPRECATED_SAVE_DUMMY_FRAME_TOS_P ())
874 DEPRECATED_SAVE_DUMMY_FRAME_TOS (sp);
04714b91 875
74cfe982
AC
876 /* Now proceed, having reached the desired place. */
877 clear_proceed_status ();
878
879 /* Create a momentary breakpoint at the return address of the
880 inferior. That way it breaks when it returns. */
04714b91 881
74cfe982
AC
882 {
883 struct breakpoint *bpt;
884 struct symtab_and_line sal;
885 struct frame_id frame;
886 init_sal (&sal); /* initialize to zeroes */
887 sal.pc = bp_addr;
888 sal.section = find_pc_overlay (sal.pc);
889 /* Set up a frame ID for the dummy frame so we can pass it to
890 set_momentary_breakpoint. We need to give the breakpoint a
0ba6dca9
AC
891 frame ID so that the breakpoint code can correctly re-identify
892 the dummy breakpoint. */
3e210248
AC
893 if (gdbarch_unwind_dummy_id_p (current_gdbarch))
894 {
895 /* Sanity. The exact same SP value is returned by
896 PUSH_DUMMY_CALL, saved as the dummy-frame TOS, and used by
897 unwind_dummy_id to form the frame ID's stack address. */
898 gdb_assert (DEPRECATED_USE_GENERIC_DUMMY_FRAMES);
899 frame = frame_id_build (sp, sal.pc);
900 }
0ba6dca9 901 else
3e210248
AC
902 {
903 /* The assumption here is that push_dummy_call() returned the
904 stack part of the frame ID. Unfortunatly, many older
905 architectures were, via a convoluted mess, relying on the
906 poorly defined and greatly overloaded
907 DEPRECATED_TARGET_READ_FP or DEPRECATED_FP_REGNUM to supply
908 the value. */
909 if (DEPRECATED_TARGET_READ_FP_P ())
910 frame = frame_id_build (DEPRECATED_TARGET_READ_FP (), sal.pc);
911 else if (DEPRECATED_FP_REGNUM >= 0)
912 frame = frame_id_build (read_register (DEPRECATED_FP_REGNUM), sal.pc);
913 else
914 frame = frame_id_build (sp, sal.pc);
915 }
74cfe982
AC
916 bpt = set_momentary_breakpoint (sal, frame, bp_call_dummy);
917 bpt->disposition = disp_del;
918 }
04714b91 919
74cfe982
AC
920 /* Execute a "stack dummy", a piece of code stored in the stack by
921 the debugger to be executed in the inferior.
04714b91 922
74cfe982
AC
923 The dummy's frame is automatically popped whenever that break is
924 hit. If that is the first time the program stops,
925 call_function_by_hand returns to its caller with that frame
926 already gone and sets RC to 0.
927
928 Otherwise, set RC to a non-zero value. If the called function
929 receives a random signal, we do not allow the user to continue
930 executing it as this may not work. The dummy frame is poped and
931 we return 1. If we hit a breakpoint, we leave the frame in place
932 and return 2 (the frame will eventually be popped when we do hit
933 the dummy end breakpoint). */
04714b91 934
74cfe982
AC
935 {
936 struct cleanup *old_cleanups = make_cleanup (null_cleanup, 0);
937 int saved_async = 0;
938
939 /* If all error()s out of proceed ended up calling normal_stop
940 (and perhaps they should; it already does in the special case
941 of error out of resume()), then we wouldn't need this. */
942 make_cleanup (breakpoint_auto_delete_contents, &stop_bpstat);
943
944 disable_watchpoints_before_interactive_call_start ();
945 proceed_to_finish = 1; /* We want stop_registers, please... */
946
947 if (target_can_async_p ())
948 saved_async = target_async_mask (0);
949
950 proceed (real_pc, TARGET_SIGNAL_0, 0);
951
952 if (saved_async)
953 target_async_mask (saved_async);
954
955 enable_watchpoints_after_interactive_call_stop ();
04714b91 956
74cfe982 957 discard_cleanups (old_cleanups);
52557533 958 }
04714b91 959
52557533
AC
960 if (stopped_by_random_signal || !stop_stack_dummy)
961 {
962 /* Find the name of the function we're about to complain about. */
edcf254d 963 const char *name = NULL;
04714b91 964 {
52557533
AC
965 struct symbol *symbol = find_pc_function (funaddr);
966 if (symbol)
967 name = SYMBOL_PRINT_NAME (symbol);
968 else
04714b91 969 {
52557533
AC
970 /* Try the minimal symbols. */
971 struct minimal_symbol *msymbol = lookup_minimal_symbol_by_pc (funaddr);
972 if (msymbol)
973 name = SYMBOL_PRINT_NAME (msymbol);
974 }
edcf254d
AC
975 if (name == NULL)
976 {
977 /* Can't use a cleanup here. It is discarded, instead use
978 an alloca. */
979 char *tmp = xstrprintf ("at %s", local_hex_string (funaddr));
980 char *a = alloca (strlen (tmp) + 1);
981 strcpy (a, tmp);
982 xfree (tmp);
983 name = a;
984 }
52557533 985 }
52557533
AC
986 if (stopped_by_random_signal)
987 {
988 /* We stopped inside the FUNCTION because of a random
989 signal. Further execution of the FUNCTION is not
990 allowed. */
04714b91 991
52557533
AC
992 if (unwind_on_signal_p)
993 {
994 /* The user wants the context restored. */
995
996 /* We must get back to the frame we were before the
997 dummy call. */
998 frame_pop (get_current_frame ());
04714b91 999
52557533
AC
1000 /* FIXME: Insert a bunch of wrap_here; name can be very
1001 long if it's a C++ name with arguments and stuff. */
1002 error ("\
04714b91
AC
1003The program being debugged was signaled while in a function called from GDB.\n\
1004GDB has restored the context to what it was before the call.\n\
1005To change this behavior use \"set unwindonsignal off\"\n\
1006Evaluation of the expression containing the function (%s) will be abandoned.",
52557533
AC
1007 name);
1008 }
1009 else
1010 {
1011 /* The user wants to stay in the frame where we stopped
1012 (default).*/
1013 /* If we restored the inferior status (via the cleanup),
1014 we would print a spurious error message (Unable to
1015 restore previously selected frame), would write the
1016 registers from the inf_status (which is wrong), and
1017 would do other wrong things. */
1018 discard_cleanups (inf_status_cleanup);
1019 discard_inferior_status (inf_status);
1020 /* FIXME: Insert a bunch of wrap_here; name can be very
1021 long if it's a C++ name with arguments and stuff. */
1022 error ("\
04714b91
AC
1023The program being debugged was signaled while in a function called from GDB.\n\
1024GDB remains in the frame where the signal was received.\n\
1025To change this behavior use \"set unwindonsignal on\"\n\
1026Evaluation of the expression containing the function (%s) will be abandoned.",
52557533
AC
1027 name);
1028 }
1029 }
04714b91 1030
52557533
AC
1031 if (!stop_stack_dummy)
1032 {
1033 /* We hit a breakpoint inside the FUNCTION. */
1034 /* If we restored the inferior status (via the cleanup), we
1035 would print a spurious error message (Unable to restore
1036 previously selected frame), would write the registers
1037 from the inf_status (which is wrong), and would do other
1038 wrong things. */
1039 discard_cleanups (inf_status_cleanup);
1040 discard_inferior_status (inf_status);
1041 /* The following error message used to say "The expression
1042 which contained the function call has been discarded."
1043 It is a hard concept to explain in a few words. Ideally,
1044 GDB would be able to resume evaluation of the expression
1045 when the function finally is done executing. Perhaps
1046 someday this will be implemented (it would not be easy). */
1047 /* FIXME: Insert a bunch of wrap_here; name can be very long if it's
1048 a C++ name with arguments and stuff. */
1049 error ("\
04714b91
AC
1050The program being debugged stopped while in a function called from GDB.\n\
1051When the function (%s) is done executing, GDB will silently\n\
1052stop (instead of continuing to evaluate the expression containing\n\
1053the function call).", name);
52557533
AC
1054 }
1055
1056 /* The above code errors out, so ... */
1057 internal_error (__FILE__, __LINE__, "... should not be here");
1058 }
04714b91 1059
74cfe982
AC
1060 /* If we get here the called FUNCTION run to completion. */
1061
1062 /* On normal return, the stack dummy has been popped already. */
1063 regcache_cpy_no_passthrough (retbuf, stop_registers);
1064
1065 /* Restore the inferior status, via its cleanup. At this stage,
1066 leave the RETBUF alone. */
1067 do_cleanups (inf_status_cleanup);
1068
1069 /* Figure out the value returned by the function. */
1070 /* elz: I defined this new macro for the hppa architecture only.
1071 this gives us a way to get the value returned by the function
1072 from the stack, at the same address we told the function to put
1073 it. We cannot assume on the pa that r28 still contains the
1074 address of the returned structure. Usually this will be
1075 overwritten by the callee. I don't know about other
1076 architectures, so I defined this macro */
04714b91 1077#ifdef VALUE_RETURNED_FROM_STACK
74cfe982
AC
1078 if (struct_return)
1079 {
1080 do_cleanups (retbuf_cleanup);
1081 return VALUE_RETURNED_FROM_STACK (value_type, struct_addr);
1082 }
04714b91 1083#endif
74cfe982
AC
1084 /* NOTE: cagney/2002-09-10: Only when the stack has been correctly
1085 aligned (using frame_align()) do we can trust STRUCT_ADDR and
1086 fetch the return value direct from the stack. This lack of trust
1087 comes about because legacy targets have a nasty habit of
1088 silently, and local to PUSH_ARGUMENTS(), moving STRUCT_ADDR. For
1089 such targets, just hope that value_being_returned() can find the
1090 adjusted value. */
1091 if (struct_return && gdbarch_frame_align_p (current_gdbarch))
1092 {
1093 struct value *retval = value_at (value_type, struct_addr, NULL);
1094 do_cleanups (retbuf_cleanup);
1095 return retval;
1096 }
1097 else
1098 {
4e7d7511
MS
1099 struct value *retval = value_being_returned (value_type, retbuf,
1100 struct_return);
74cfe982
AC
1101 do_cleanups (retbuf_cleanup);
1102 return retval;
1103 }
04714b91
AC
1104}
1105
1106void _initialize_infcall (void);
1107
1108void
1109_initialize_infcall (void)
1110{
1111 add_setshow_boolean_cmd ("coerce-float-to-double", class_obscure,
1112 &coerce_float_to_double_p, "\
1113Set coercion of floats to doubles when calling functions\n\
1114Variables of type float should generally be converted to doubles before\n\
1115calling an unprototyped function, and left alone when calling a prototyped\n\
1116function. However, some older debug info formats do not provide enough\n\
1117information to determine that a function is prototyped. If this flag is\n\
1118set, GDB will perform the conversion for a function it considers\n\
1119unprototyped.\n\
1120The default is to perform the conversion.\n", "\
1121Show coercion of floats to doubles when calling functions\n\
1122Variables of type float should generally be converted to doubles before\n\
1123calling an unprototyped function, and left alone when calling a prototyped\n\
1124function. However, some older debug info formats do not provide enough\n\
1125information to determine that a function is prototyped. If this flag is\n\
1126set, GDB will perform the conversion for a function it considers\n\
1127unprototyped.\n\
1128The default is to perform the conversion.\n",
1129 NULL, NULL, &setlist, &showlist);
1130
1131 add_setshow_boolean_cmd ("unwindonsignal", no_class,
1132 &unwind_on_signal_p, "\
1133Set unwinding of stack if a signal is received while in a call dummy.\n\
1134The unwindonsignal lets the user determine what gdb should do if a signal\n\
1135is received while in a function called from gdb (call dummy). If set, gdb\n\
1136unwinds the stack and restore the context to what as it was before the call.\n\
1137The default is to stop in the frame where the signal was received.", "\
1138Set unwinding of stack if a signal is received while in a call dummy.\n\
1139The unwindonsignal lets the user determine what gdb should do if a signal\n\
1140is received while in a function called from gdb (call dummy). If set, gdb\n\
1141unwinds the stack and restore the context to what as it was before the call.\n\
1142The default is to stop in the frame where the signal was received.",
1143 NULL, NULL, &setlist, &showlist);
1144}