Go to file
Joel Brobecker 66fc87a0d5 Add gdb.ada/info_addr_mixed_case new testcase
This patch adds a new testcase to demonstrate a regression introduced by:

    commit b5ec771e60
    Date:   Wed Nov 8 14:22:32 2017 +0000
    Subject: Introduce lookup_name_info and generalize Ada's FULL/WILD name matching

The purpose of the testcase is to verify that a user can use any
casing for an Ada symbol name passed to the "info address" command.
After the patch above was applied, GDB was no longer able to find
the symbol:

    (gdb) info address My_Table
    No symbol "My_Table" in current context.

gdb/testsuite/ChangeLog:

	PR gdb/22670
	* gdb.ada/info_addr_mixed_case: New testcase.

Tested on x86_64-linux, both before and after the patch.
2018-01-04 03:30:06 -05:00
bfd Automatic date update in version.in 2018-01-04 00:00:20 +00:00
binutils Fix compile time warning introduced by previous delta. 2018-01-03 17:32:59 +00:00
config
cpu
elfcpp Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
etc Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
gas Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
gdb Add gdb.ada/info_addr_mixed_case new testcase 2018-01-04 03:30:06 -05:00
gold Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
gprof Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
include Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
intl
ld Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
libdecnumber
libiberty
opcodes Update year range in copyright notice of binutils files 2018-01-03 17:49:56 +10:30
readline
sim Fix compile time warning (in the ARM simulator) about a print statement with insufficient arguments. 2018-01-02 17:15:16 +00:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
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
README
README-maintainer-mode
setup.com
src-release.sh
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.