Go to file
Jan Vrany 37e5833da5 gdb: fix command lookup in execute_command ()
Commit b5661ff2 ("gdb: fix possible use-after-free when
executing commands") used lookup_cmd_exact () to lookup
command again after its execution to avoid possible
use-after-free error.

However this change broke test gdb.base/define.exp which
defines a post-hook for subcommand ("target testsuite").
In this case,  lookup_cmd_exact () returned NULL because
there's no command 'testsuite' in top-level commands.

This commit fixes this case by looking up the command again
using the original command line via lookup_cmd ().

Approved-By: Simon Marchi <simon.marchi@efficios.com>
2022-12-19 11:24:36 +00:00
bfd Automatic date update in version.in 2022-12-19 00:01:23 +00:00
binutils Fix potential illegal memory accesses when parsing corrupt DWARF data. 2022-12-19 11:13:46 +00:00
config
contrib
cpu
elfcpp
etc
gas Arm: break gas dependency on libopcodes 2022-12-19 09:23:13 +01:00
gdb gdb: fix command lookup in execute_command () 2022-12-19 11:24:36 +00:00
gdbserver [aarch64] Fix removal of non-address bits for PAuth 2022-12-16 11:18:32 +00:00
gdbsupport gdbsupport: add string_xml_appendf 2022-12-16 08:33:12 -05:00
gnulib
gold New Romainian translation for the GOLD subdirectory. 2022-12-19 09:47:36 +00:00
gprof
gprofng gprofng/testsuite: skip Java test without JDK 2022-12-19 09:36:21 +01:00
include libsframe: provide new access API for mangled RA bit 2022-12-16 22:01:57 -08:00
intl
ld ld bootstrap test in build dir with path containing symlinks 2022-12-18 19:11:32 +10:30
libbacktrace testsuite: support mold linker 2022-12-05 15:52:51 +01:00
libctf libctf: remove unnecessary zstd constructs 2022-12-12 10:53:39 -08:00
libdecnumber
libiberty
libsframe sframe: doc: update spec for the mangled-RA bit in FRE 2022-12-16 22:02:11 -08:00
opcodes x86: omit Cpu prefixes from opcode table 2022-12-19 09:22:33 +01:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.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 src-release.sh: Fix gdb source tarball build failure due to libsframe 2022-11-30 07:32:58 +04: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.