Go to file
Nick Alcock 0daea2d62c
libctf: fix ref leak of names of newly-inserted non-root-visible types
A bug in ctf_dtd_delete led to refs in the string table to the
names of non-root-visible types not being removed when the DTD
was.  This seems harmless, but actually it would lead to a write
down a pointer into freed memory if such a type was ctf_rollback()ed
over and then the dict was serialized (updating all the refs as the
strtab was serialized in turn).

Bug introduced in commit fe4c2d5563
("libctf: create: non-root-visible types should not appear in name tables")
which is included in binutils 2.35.

libctf/
	* ctf-create.c (ctf_dtd_delete): Remove refs for all types
	with names, not just root-visible ones.
2024-08-02 11:56:42 +01:00
bfd s390: Add DT_JMPREL pointing to .rela.[i]plt with static-pie 2022-04-28 14:54:50 +02:00
binutils PR28540, segmentation fault on NULL byte_get 2021-11-04 14:23:52 +10:30
config
contrib
cpu Re: opcodes: constify & local meps macros 2021-07-29 14:38:44 +09:30
elfcpp This is the 2.37 release 2021-07-18 17:46:54 +01:00
etc texi2pod.pl: add no-op --no-split option support [PR28144] 2021-07-29 14:29:45 +09:30
gas IBM zSystems: Add support for z16 as CPU name. 2022-04-07 08:21:14 +02:00
gdb
gdbserver
gdbsupport
gnulib
gold gold: Place .note.gnu.property section before other note sections 2021-11-11 13:25:16 -08:00
gprof This is the 2.37 release 2021-07-18 17:46:54 +01:00
include Revert: [AArch64] MTE corefile support 2021-09-07 10:35:11 -03:00
intl
ld i386: Allow GOT32 relocations against ABS symbols 2022-02-07 16:13:51 -08:00
libctf libctf: fix ref leak of names of newly-inserted non-root-visible types 2024-08-02 11:56:42 +01:00
libdecnumber
libiberty Change "uint" to "unsigned" 2021-07-19 21:02:21 +09:30
opcodes IBM zSystems: Add support for z16 as CPU name. 2022-04-07 08:21:14 +02:00
readline
sim
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog This is the 2.37 release 2021-07-18 17:46:54 +01:00
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.