c0d1d88354
* i386-tdep.c: Include "symfile.h". (i386_frameless_signal_p): Consider a function to be frameless if the pc points at the first instruction of the function. (i386_frame_chain): Handle (generic) call dummies. (i386_frame_saved_pc): Likewise. (i386_frame_init_saved_regs): Remove code dealing with call dummies on the stack. (i386_push_dummy_frame): Removed. (i386_call_dummy_words): Removed. (i386_fix_call_dummy): Removed. (i386_push_return_address): New function. (i386_do_pop_frame): Renamed from i386_pop_frame. Add FRAME parameter, and don't call get_current_frame. (i386_pop_frame): New function. (i386_gdbarch_init): Set use_generic_dummy_frames to 1, set call_dummy_location to AT_ENTRY_POINT, set call_dummy_address to entry_point_address, set call_dummy_breakpoint_offset to 0, set call_dummy_length to 0, set call_dummy_words to NULL, set sizeof_call_dummy_words to 0, set fix_call_dummy to generic_fix_call_dummy, set pc_in_call_dummy to pc_in_call_dummy_at_entry_point, set push_dummy_frame to generic_push_dummy_frame, set push_return_address to i386_push_return_address and set frame_chain_valid to generic_file_frame_chain_valid.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.