Go to file
Tom de Vries d191d716f3 [gdb/testsuite] Fix maint-expand-symbols-header-file.exp for cc-with-gdb-index
With test-case gdb.base/maint-expand-symbols-header-file.exp and target board
cc-with-gdb-index, we have:
...
FAIL: gdb.base/maint-expand-symbols-header-file.exp: \
  verify no symtabs are expanded
...

By default, with partial symbols, we find the main function in the partial
symbols, and derive the initial language setting from that, without expanding
any psymtab.

But that doesn't work with the indices, because the indices don't store the
language with the symbols.  So instead, the main psymtab is expanded to get
the language of main, which causes the FAIL.

Fix this by manually setting the language.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-04-16  Tom de Vries  <tdevries@suse.de>

	* gdb.base/maint-expand-symbols-header-file.exp: Set language before
	loading exec.
2020-04-16 08:40:19 +02:00
bfd PowerPC64 GOT reloc reserving PLT entry for ifunc 2020-04-16 15:43:19 +09:30
binutils Extend objdump --no-addresses info 2020-04-16 12:53:55 +09:30
config
contrib
cpu
elfcpp
etc
gas x86: Correct -mlfence-before-indirect-branch= documentation 2020-04-08 19:31:45 -07:00
gdb [gdb/testsuite] Fix maint-expand-symbols-header-file.exp for cc-with-gdb-index 2020-04-16 08:40:19 +02:00
gdbserver gdbserver: fix format string warning in win32-low.cc 2020-04-15 21:09:17 -04:00
gdbsupport Move gdb_notifier comment 2020-04-13 14:10:04 -06:00
gnulib
gold
gprof Updated Serbian translation for the gprof subdirectory 2020-04-01 14:37:02 +01:00
include Unify the behaviour of ld.bfd and ld.gold with respect to warning about unresolved symbol references. (PR 24613) 2020-04-15 14:25:08 +01:00
intl
ld Unify the behaviour of ld.bfd and ld.gold with respect to warning about unresolved symbol references. (PR 24613) 2020-04-15 14:25:08 +01:00
libctf
libdecnumber
libiberty
opcodes Add support for intel TSXLDTRK instructions$ 2020-04-07 13:59:50 +08:00
readline
sim
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
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
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
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.