gdb/gdb/infcall.c

69    in a function called from gdb (call dummy).  If set, gdb unwinds
233   /* NOTE: This is pretty wierd, as the call dummy is actually a
241   ULONGEST *dummy = alloca (DEPRECATED_SIZEOF_CALL_DUMMY_WORDS);
246   memcpy (dummy, DEPRECATED_CALL_DUMMY_WORDS,
261      after allocating space for the call dummy.  A target can specify
268     for (i = 0; i < (int) (DEPRECATED_SIZEOF_CALL_DUMMY_WORDS / sizeof (dummy[0]));
272 			      (ULONGEST) dummy[i]);
293   /* Yes, the offset is applied to the real_pc and not the dummy addr.
363 /* All this stuff with a dummy frame may seem unnecessarily complicated
364    (why not just save registers in GDB?).  The purpose of pushing a dummy
370    making dummy frames be different from normal frames, consider that.  */
426       to extract the generic dummy frame code from the architecture
430       thread OR frame OR ptid as a parameter, and returns a dummy
433       about it, since everything is ment to be using generic dummy
434       frames, why not even use some of the dummy frame code to here -
439       dummy frame and fix one of those nasty lost struct return edge
463 	   On a RISC architecture, a void parameterless generic dummy
469 	   void parameterless generic dummy frame calls to frameless
473 	   infinite loop --- when GDB tries to find a generic dummy
474 	   frame on the internal dummy frame stack, it will always
478 	   stack.  That way, two dummy frames can never be identical.
498 	 If the generic dummy frame ends up empty (because nothing is
572       /* A call dummy always consists of just a single breakpoint, so
573          it's address is the same as the address of the dummy.  */
595 	/* A call dummy always consists of just a single breakpoint,
596 	   so it's address is the same as the address of the dummy.  */
606        dummy-frame code is later able to re-identify it.  */
768   /* Create the dummy stack frame.  Pass in the call dummy address as,
769      presumably, the ABI code knows where, in the call dummy, the
839 	 PUSH_DUMMY_CALL, saved as the dummy-frame TOS, and used by
860     /* Set up a frame ID for the dummy frame so we can pass it to
863        the dummy breakpoint.  */
867 	 PUSH_DUMMY_CALL, saved as the dummy-frame TOS, and used by
891   /* Execute a "stack dummy", a piece of code stored in the stack by
894      The dummy's frame is automatically popped whenever that break is
901      executing it as this may not work.  The dummy frame is poped and
904      the dummy end breakpoint).  */
968 		 dummy call. */
1033   /* On normal return, the stack dummy has been popped already.  */
1092 Set unwinding of stack if a signal is received while in a call dummy.\n\
1094 is received while in a function called from gdb (call dummy).  If set, gdb\n\
1097 Set unwinding of stack if a signal is received while in a call dummy.\n\
1099 is received while in a function called from gdb (call dummy).  If set, gdb\n\