Go to file
Andrew Burgess 1720b64f73 gdb: fix possible nullptr dereference in a remote_debug_printf call
While working on another patch I triggered a segfault from within the
function remote_target::discard_pending_stop_replies.  Turns out this
was caused by a cut&paste error introduced in this commit:

  commit df5ad10200
  Date:   Wed Dec 1 09:40:03 2021 -0500

      gdb, gdbserver: detach fork child when detaching from fork parent

This commit adds a remote_debug_printf call that was copied from
earlier in the function, however, the new call wasn't updated to use
the appropriate local variable.  The local variable that it is using
might be nullptr, in which case we trigger undefined behaviour, and
could crash, which is what I was seeing.

Fixed by updating to use the correct local variable.
2023-08-03 09:54:27 +01:00
bfd RISC-V: Add support for 'Zvfh' and 'Zvfhmin' 2023-08-03 05:58:21 +00:00
binutils Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
config
contrib
cpu
elfcpp
etc
gas Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
gdb gdb: fix possible nullptr dereference in a remote_debug_printf call 2023-08-03 09:54:27 +01:00
gdbserver
gdbsupport
gnulib
gold Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
gprof Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
gprofng Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
include Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
intl
ld Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
libbacktrace
libctf
libdecnumber
libiberty
libsframe
opcodes Fix Wlto-type-mismatch in opcodes/ft32-dis.c 2023-08-03 09:48:58 +01:00
readline
sim bpf: sim: do not overflow instruction immediates in tests 2023-07-31 11:09:47 +02:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
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
SECURITY.txt
setup.com
src-release.sh Revert "2.41 Release sources" 2023-08-02 12:06:23 +01:00
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.