Binutils with MCST patches
Go to file
Joel Brobecker e9ef4f394d procfs.c: iterate_over_mappings callback has wrong profile.
The function proc_find_memory_regions calls iterate_over_mappings as
follow:

> return iterate_over_mappings (pi, func, data,
>                               find_memory_regions_callback);

The problem is that both func and find_memory_regions_callback
do not match the profile expected by iterate_over_mappings:

> iterate_over_mappings (procinfo *pi, int (*child_func) (), void *data,
>                        int (*func) (struct prmap *map,
>                                     int (*child_func) (),
>                                     void *data))

We cannot change proc_find_memory_regions such that FUNC is a pointer
to a function that takes no argument (in place of the 6 that it has).
This is because proc_find_memory_regions is used as a target_ops method.
However, it turns out that changing iterate_over_mappings to conform
to the profile imposed by the target_ops vector is possible without
much effort.

gdb/ChangeLog:

        * procfs.c (iterate_over_mappings_cb_ftype): New typedef.
        (iterate_over_mappings): Adjust function profile. Add declaration.
        (insert_dbx_link_bpt_in_region, info_mappings_callback):
        Adjust accordingly.
2010-04-20 22:35:58 +00:00
bfd bfd: 2010-04-20 22:03:00 +00:00
binutils Updated French translation. 2010-04-20 09:28:15 +00:00
config Sync from gcc mainline. 2010-02-15 10:37:55 +00:00
cpu * m32r.cpu (HASH-PREFIX): Delete. 2010-02-12 04:38:21 +00:00
elfcpp include: 2010-03-05 21:04:59 +00:00
etc Regenerate tree using Autoconf 2.64 and Automake 1.11. 2009-08-22 16:56:56 +00:00
gas bfd: 2010-04-20 22:03:00 +00:00
gdb procfs.c: iterate_over_mappings callback has wrong profile. 2010-04-20 22:35:58 +00:00
gold 2010-04-18 Sriraman Tallam <tmsriram@google.com> 2010-04-20 21:13:30 +00:00
gprof * configure: Regenerate. 2010-04-07 07:20:51 +00:00
include * ld/testsuite/ld-arm/attr-merge-2.attr: Update for changes in attribute output. 2010-04-15 10:56:39 +00:00
intl merge from gcc 2010-04-05 18:02:22 +00:00
ld bfd: 2010-04-20 22:03:00 +00:00
libdecnumber merge from gcc 2010-04-05 18:02:22 +00:00
libiberty merge from gcc 2010-04-07 21:16:24 +00:00
opcodes Remove extra breack. 2010-04-16 21:37:08 +00:00
readline Regenerate tree using Autoconf 2.64 and Automake 1.11. 2009-08-22 16:56:56 +00:00
sim sim: mn10300: convert to new sockser status code 2010-04-19 19:03:28 +00:00
texinfo
.cvsignore
ChangeLog 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
compile Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00
config-ml.in
config.guess * config.sub: Update to version 2010-03-22. 2010-03-23 14:27:19 +00:00
config.rpath
config.sub * config.sub: Update to version 2010-03-22. 2010-03-23 14:27:19 +00:00
configure 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
configure.ac 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
COPYING.NEWLIB 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
depcomp Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00
djunpack.bat
install-sh Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00
libtool.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
lt~obsolete.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltgcc.m4
ltmain.sh Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltoptions.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltsugar.m4
ltversion.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
MAINTAINERS * MAINTAINERS: Perform some obvious fixups. 2009-08-19 02:53:50 +00:00
Makefile.def Merge from gcc: 2010-03-14 16:00:37 +00:00
Makefile.in Merge from gcc: 2010-03-14 16:00:37 +00:00
Makefile.tpl * Makefile.tpl: Use "-exec rm {}" rather than "-delete" to delete 2010-02-17 11:02:54 +00:00
makefile.vms
missing Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00
mkdep
mkinstalldirs Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00
move-if-change
README
README-maintainer-mode Cleanups after the update to Autoconf 2.64, Automake 1.11. 2009-08-22 17:08:11 +00:00
setup.com 2009-09-01 Tristan Gingold <gingold@adacore.com> 2009-09-01 13:38:26 +00:00
src-release
symlink-tree
ylwrap Update automake-provided files in the toplevel. 2009-08-22 11:48:33 +00:00

		   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.