GDB that can debug Mach-Os on Linux
Go to file
Jim Blandy 84f0252a03 Expand preprocessor macros in C expressions.
* c-lang.h: #include "macroexp.h", for macro_lookup_ftype.
(scan_macro_expansion, scanning_macro_expansion,
finished_macro_expansion): New function declarations.
(expression_macro_lookup_func, expression_macro_lookup_baton): New
variable declarations.
* parser-defs.h (expression_context_pc): New declaration.
* parse.c (expression_context_pc): New variable.
(parse_exp_1): Set expression_context_pc, as well as
expression_context_block.
* c-exp.y (yylex): If we're not already reading the result of a
macro expansion, try to macro-expand the next token.  When we're
done scanning a macro expansion, switch back to the mainline text.
Commas and `if's in a macro's expansion don't terminate the input.
* c-lang.c: #include "macroscope.h" and "gdb_assert.h".
(macro_original_text, macro_expanded_text,
expression_macro_lookup_func, expression_macro_lookup_baton): New
variables.
(scan_macro_expansion, scanning_macro_expansion,
finished_macro_expansion, scan_macro_cleanup, null_macro_lookup,
c_preprocess_and_parse): New functions.
(c_language_defn, cplus_language_defn, asm_language_defn): Call
c_preprocess_and_parse, instead of c_parse.
* Makefile.in (c_lang_h): Note that this #includes macroexp.h.
(c-lang.o): Note dependency on macroscope.h and gdb_assert.h.
2002-05-17 17:57:48 +00:00
bfd * elf64-ppc.c (ppc64_elf_info_to_howto): Formatting. 2002-05-17 13:25:04 +00:00
binutils * MAINTAINERS: Add myself as the second AVR port maintainer. 2002-05-16 18:53:23 +00:00
config
etc
gas Remove stale files. 2002-05-17 10:36:51 +00:00
gdb Expand preprocessor macros in C expressions. 2002-05-17 17:57:48 +00:00
gprof
include print_insn_sh cleanup: 2002-05-17 14:36:46 +00:00
intl
ld * Makefile.am: Add new emulations avr1, avr2, avr3, avr4, avr5. 2002-05-17 05:55:14 +00:00
libiberty
mmalloc
opcodes print_insn_sh cleanup: 2002-05-17 14:36:46 +00:00
readline
sim print_insn_sh cleanup: 2002-05-17 14:36:46 +00:00
texinfo
.cvsignore
ChangeLog
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
symlink-tree
ylwrap

		   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.