inferior functions and return various types.
* gdb.base/callfuncs.c: Add functions to receive a struct
and return a member of the struct, in various types.
before trying to determine the start of the function.
(skip_prologue): Skip subroutine call which might save the
floating point registers only if it is within the first three
instructions.
Reinstate setting of alloca_reg if setup of a gcc frame pointer
is found.
(frame_get_cache_fsr): Use new fields in rs6000_framedata.
is bash or ksh, which handles "... $(TCL) ..." by trying to run TCL.
Changed configure.in and regenerated configure, including two lines
apparently inserted by custom cygnus version of autoconf 2.4.
read_next_frame_reg to alpha_find_saved_regs, handle saved
floating point registers.
* mips-tdep.c: Move sigtramp handling of saved registers from
read_next_frame_reg to mips_find_saved_regs, handle saved
floating point registers.
* config/mips/tm-irix3.h, config/mips/tm-irix5.h,
config/mips/tm-mipsv4.h (SIGFRAME_FPREGSAVE_OFF): Define.
* sparc-tdep.c (sparc_pc_adjust): Fix check for `unimp'
instruction to handle functions returning structures with
large sizes properly.
"call function when asleep" and "send end of file".
* gdb.base/corefile.exp: Add "i*86-*-linuxaout" to xfail list
for "backtrace in corefile.exp".
* gdb.base/a1-selftest.exp: Add "i*86-*-linux*" to xfail list
for "backtrace through signal handler".
* gdb.base/corefile.exp: Make sure we actually generate a core file
before trying the core tests. Some systems allow the user to suppress
generation of core files and default to that (linux for example).
* gdb.base/signals.exp: Change xfail for "next" acting like "continue"
from "i*86-*-linux" to "i*86-*-linuxaout". Works with ELF beta.
and for thread_alive change from a couple weeks ago.
(extended_remote_ops): Declare and define a new target vector
for the extended remote protocol.
(extended_remote_restart): New function to restart the remote
server & process.
(remote_open): Just a stub routine.
(extended_remote_open): New function to start a remote session
using the extended gdb remote protocol.
(remote_open_1): New function containing code common to both
remote_open and extended_remote_open.
(remote_mourn, extended_remote_mourn, remote_mourn_1): Similarly.
(extended_remote_create_inferior): New function for the extended
remote target.
(initialize_remote): Add the extended_remote_ops target vector.
* gdbserver/server.c (main, case '!'): Set extended_protocol.
(main, case 'k'): If the extended protocol is in use, kill the
inferior then start a new one.
(main, case 'R'): New command to restart the remote server and
inferior process. Only supported when using the extended
protocol.
(main, server loop): If the inferior terminates while using the
extended protocol then start a new one. If getpkt fails when
using the extended protocol then exit.
New extended remote gdb protocol support; intended mainly for use with
the gdbserver testing framework that I'll be checking in soon. Also
useful for interactive remote debugging since it supports "run".
gdb tests (step.exp and step2.exp).
* config/mt-lynx (STEP_EXECUTABLE): Define.
(THREADFLAGS): Define.
Hiro's test for 6100 and a crude test of my own. They both need some
major cleanup for non-lynx hosts; both are also a little too loose in
their checks. But I'm too burnt out on lynx to address either concern.
further notice.
Looks like a bug in the lynx2.2.2 kernel scroggs the stack pointer in
these tests leading to massive failures. I've sent a nice small concise
example to Mark Rome @ lynx. Severe braindamage.
typo in setting up configdirs for native builds.
* gdb.base/return.exp: Fix typo in return double test.
* gdb.base/return.c (tmp2, tmp3): Made global to inhibit the
compiler from optimizing them away.
means the process is single threaded, so there's no need to add
it to the thread list. Handle case where multi-threaded process
reverts back to a single-threaded process.
after the inferior gdb has started.
'cuz lynx may take a couple minutes to start the inferior gdb...
* gdb.base/a2-run.exp: Handle gdb echoing more than one cr-lf
after each command.
* gdb.base/funcargs.exp: Likewise.
* gdb.base/gdbvars.exp: Likewise.
* gdb.base/interrupt.exp: Likewise.
* gdb.base/list.exp: Likewise.
* gdb.base/watchpoint.exp: Likewise.
* gdb.c++/demangle.exp: Likewise.
* gdb.c++/inherit.exp: Likewise.
* gdb.chill/chexp.exp: Likewise.
* gdb.fortran/exprs.exp: Likewise.
Just in case we can't get a version of expect that sets the tty modes
right on lynx to avoid this problem.
started after sending a "run" command to gdb.
(text_next_with_recursion): Don't check the output from the
program's printf statement. Instead just make sure the program
exited.
