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