Kevin Buettner
4ba11f89a2
When making a core file with the GDB's gcore command on Linux, the same criteria used for determining which mappings should be dumped were also being used for determining which entries should be placed in the NT_FILE note. This is wrong; we want to place all file-backed mappings in this note. The predicate function, dump_mapping_p, was used to determine whether or not to dump a mapping from within linux_find_memory_regions_full. This commit leaves this predicate in place, but adds a new parameter, should_dump_mapping_p, to linux_find_memory_regions_full. It then calls should_dump_mapping_p instead of dump_mapping_p. dump_mapping_p is passed to linux_find_memory_regions_full at one call site; at the other call site, dump_note_entry_p is passed instead. gdb/ChangeLog: * linux-tdep.c (dump_note_entry_p): New function. (linux_dump_mapping_p_ftype): New typedef. (linux_find_memory_regions_full): Add new parameter, should_dump_mapping_p. (linux_find_memory_regions): Adjust call to linux_find_memory_regions_full. (linux_make_mappings_core_file_notes): Use dump_note_entry_p in call to linux_find_memory_regions_full.
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.