Go to file
Joel Brobecker bb2f58dc41 Use symbol search name in expand_symtabs_matching_via_partial...
We are iterating over all symbols in a partial symtab that would
match a given name, so we should match the partial symbols
search name against the given name rather than using the natural
name.  In C++, that does not make a difference, but it does in
Ada, because Ada searches using the symbol encoded name...

We also update the generation of the .gdb_index file to match this
change in the search. Although technically an incompatible change,
we do not increment the gdb_index version number, because Ada is
the only language where it would make a difference - except that
this feature is not supported for Ada.

gdb/ChangeLog:

        * psymtab.c (expand_symtabs_matching_via_partial): Match
        the partial symbols using their SYMBOL_SEARCH_NAME.
        * symfile.h (struct quick_symbol_functions): Udate the
        documentation of expand_symtabs_matching.
        * dwarf2read.c (write_psymbols): Use SYMBOL_SEARCH_NAME instead
        of SYMBOL_NATURAL_NAME in index entry.
2011-12-21 07:34:09 +00:00
bfd bfd: 2011-12-19 15:42:37 +00:00
binutils
config config/: 2011-12-20 17:01:30 +00:00
cpu
elfcpp
etc
gas bfd: 2011-12-19 15:42:37 +00:00
gdb Use symbol search name in expand_symtabs_matching_via_partial... 2011-12-21 07:34:09 +00:00
gold * object.h (Relobj::local_symbol_value): New function. 2011-12-19 21:07:16 +00:00
gprof
include 2011-12-19 Chung-Lin Tang <cltang@codesourcery.com> 2011-12-19 07:58:02 +00:00
intl
ld * emulparams/elf32bmip.sh (OTHER_SECTIONS): Put .mdebug.* and 2011-12-20 17:55:24 +00:00
libdecnumber config/: 2011-12-20 17:01:30 +00:00
libiberty merge from gcc 2011-12-20 19:02:08 +00:00
opcodes
readline
sim Work around Solaris bourne shell limitation when building the sim 2011-12-19 04:33:39 +00:00
texinfo
.cvsignore
.gitignore
ChangeLog * configure: Regenerate. 2011-12-18 10:20:52 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure * configure: Regenerate. 2011-12-18 10:20:52 +00:00
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.