Go to file
Tom Tromey a15a276b46 Avoid crash in Ada value printing with optimized-out array
The Ada value-printing code could crash when printing an array which
had been optimized out.

The crash is difficult to reproduce, but I did manage to write a test
that at least shows that the previous behavior was incorrect -- before
the patch, the array is printed as if it is valid and every value is 0.

gdb/ChangeLog
2021-04-15  Tom Tromey  <tromey@adacore.com>

	* ada-valprint.c (ada_value_print_array): Handle optimized-out
	arrays.

gdb/testsuite/ChangeLog
2021-04-15  Tom Tromey  <tromey@adacore.com>

	* gdb.dwarf2/arr-stride.exp: Add test.
2021-04-15 10:14:11 -06:00
bfd RISC-V: PR27584, surpress local and empty name symbols for nm. 2021-04-15 10:32:36 +08:00
binutils PR27734, get_stat_atime_ns/get_stat_mtime_ns might not use parameter 2021-04-16 00:09:26 +09:30
config
contrib
cpu Use bool in opcodes 2021-03-31 10:49:23 +10:30
elfcpp
etc
gas Re: PR27723, Internal error in select_cie_for_fde 2021-04-14 09:37:41 +09:30
gdb Avoid crash in Ada value printing with optimized-out array 2021-04-15 10:14:11 -06:00
gdbserver Remove use of _WIN32_WCE 2021-04-14 06:45:44 -06:00
gdbsupport New memory-tag commands 2021-03-24 14:57:53 -03:00
gnulib gnulib: import gitlog-to-changelog 2021-03-24 19:35:40 -04:00
gold PR27625, powerpc64 gold __tls_get_addr calls 2021-03-30 13:38:41 +10:30
gprof PR27716, build failure for msdosdjgpp: PATH_MAX undeclared 2021-04-14 15:06:11 +09:30
include PowerPC disassembly of pcrel references 2021-04-09 16:56:43 +09:30
intl
ld Document the effect of --as-needed on --rpath on Linux based systems. 2021-04-13 14:37:06 +01:00
libctf libctf: fix ELF-in-BFD checks in the presence of ASAN 2021-03-25 16:32:51 +00:00
libdecnumber
libiberty
opcodes ENABLE_CHECKING in bfd, opcodes, binutils, ld 2021-04-13 00:35:44 +09:30
readline
sim sim: cgen: move cgen_cpu_max_extra_bytes logic into the common code 2021-04-12 00:14:32 -04:00
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.